WebFund 2015W: Tutorial 4 - Revision history

Soma at 04:21, 2 February 2015

2015-02-02T04:21:05Z

← Older revision		Revision as of 04:21, 2 February 2015
Line 1:		Line 1:
	~~'''This tutorial is not yet finalized.'''~~

	In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/notes-demo.zip notes-demo], a simple node express application that demonstrates session support and basic form interaction. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2\|Tutorial 2]].		In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/notes-demo.zip notes-demo], a simple node express application that demonstrates session support and basic form interaction. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2\|Tutorial 2]].

Soma at 04:20, 2 February 2015

2015-02-02T04:20:14Z

← Older revision		Revision as of 04:20, 2 February 2015
Line 1:		Line 1:
	'''This tutorial is not yet finalized ~~(and in fact is likely to change radically)~~.'''		'''This tutorial is not yet finalized.'''

	In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/notes-demo.zip notes-demo], a simple node express application that demonstrates session support and basic form interaction. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2\|Tutorial 2]].		In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/notes-demo.zip notes-demo], a simple node express application that demonstrates session support and basic form interaction. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2\|Tutorial 2]].
Line 16:		Line 16:
	* What code is responsible for this difference? Specifically, what is the difference in how user data is stored or displayed?		* What code is responsible for this difference? Specifically, what is the difference in how user data is stored or displayed?

	~~To get checked off, show a TA the following:~~		===Questions to ponder===
	* A session cookie sent by the browser
	* A session cookie stored on the server
	* A modified /notes page that shows an error after attempting to edit a non-existent note

	Questions to ponder:
	* Who can observe the cookie? Modify it?		* Who can observe the cookie? Modify it?
	* How "persistent" are sessions on the server? The client?		* How "persistent" are sessions on the server? The client?
Line 27:		Line 22:
	* How much code would you have to add to [[WebFund 2015W: Tutorial 3\|tinywebserver]] in order to get it to duplicate the functionality of notes-demo?		* How much code would you have to add to [[WebFund 2015W: Tutorial 3\|tinywebserver]] in order to get it to duplicate the functionality of notes-demo?
	* Why does this application have so many screens to implement so little functionality?		* Why does this application have so many screens to implement so little functionality?
			* Can you access notes belonging to a different user without logging in as that user?

			===Getting Checked Off===

			To get checked off, show a TA the following:
			* A session cookie sent by the browser
			* A session cookie stored on the server
			* A modified /notes page that shows an error after attempting to edit a non-existent note

Soma at 04:18, 2 February 2015

2015-02-02T04:18:04Z

← Older revision		Revision as of 04:18, 2 February 2015
Line 1:		Line 1:
	'''This tutorial is not yet finalized (and in fact is likely to change radically).'''		'''This tutorial is not yet finalized (and in fact is likely to change radically).'''

	In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/~~session~~-demo.zip ~~session~~-demo], a simple node express application that demonstrates session support. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2\|Tutorial 2]].		In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/notes-demo.zip notes-demo], a simple node express application that demonstrates session support and basic form interaction. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2\|Tutorial 2]].

	In this tutorial you should do the following:		In this tutorial you should do the following after getting [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/notes-demo.zip notes-demo] running.
	* Get [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/~~session~~-demo.zip ~~session~~-demo] running.
			===Understanding Sessions===
	* Try logging in to the app using two different browsers (e.g., Firefox and Chrome). What happens when you logout from one browser - how does it affect the other?		* Try logging in to the app using two different browsers (e.g., Firefox and Chrome). What happens when you logout from one browser - how does it affect the other?
	* Observe the request and response for the app's home page (http://localhost:3000). Look at both the network panel (load the page ''after'' selecting the network panel) and the HTML DOM view (Inspector/Elements)		* Observe the request and response for the app's home page (http://localhost:3000). Look at both the network panel (load the page ''after'' selecting the network panel) and the HTML DOM view (Inspector/Elements)
Line 11:		Line 12:
	* What does the req.body and req.session look like just before a page gets rendered?		* What does the req.body and req.session look like just before a page gets rendered?

			===Understanding User input===
			* What happens to HTML tags embedded in a note title? What about the content?
			* What code is responsible for this difference? Specifically, what is the difference in how user data is stored or displayed?

	To get checked off, show a TA the following:		To get checked off, show a TA the following:
	* A session cookie sent by the browser		* A session cookie sent by the browser
	* A session cookie stored on the server		* A session cookie stored on the server
			* A modified /notes page that shows an error after attempting to edit a non-existent note

	Questions to ponder:		Questions to ponder:
Line 21:		Line 25:
	* How "persistent" are sessions on the server? The client?		* How "persistent" are sessions on the server? The client?
	* How could you "hijack" a session? Does the difficulty of session hijacking relate to whether a login is password protected or not?		* How could you "hijack" a session? Does the difficulty of session hijacking relate to whether a login is password protected or not?
	* How much code would you have to add to [[WebFund 2015W: Tutorial 3\|tinywebserver]] in order to get it to duplicate the functionality of ~~session~~-demo?		* How much code would you have to add to [[WebFund 2015W: Tutorial 3\|tinywebserver]] in order to get it to duplicate the functionality of notes-demo?
			* Why does this application have so many screens to implement so little functionality?

Soma at 17:03, 31 January 2015

2015-01-31T17:03:21Z

← Older revision		Revision as of 17:03, 31 January 2015
Line 1:		Line 1:
			'''This tutorial is not yet finalized (and in fact is likely to change radically).'''

	In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/session-demo.zip session-demo], a simple node express application that demonstrates session support. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2\|Tutorial 2]].		In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/session-demo.zip session-demo], a simple node express application that demonstrates session support. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2\|Tutorial 2]].

Soma: Created page with "In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/session-demo.zip session-demo], a simple node express application that demonstra..."

2015-01-31T16:52:33Z

Created page with "In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/session-demo.zip session-demo], a simple node express application that demonstra..."

New page

In this tutorial you will examine [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/session-demo.zip session-demo], a simple node express application that demonstrates session support. You will need to use the browser and node debugging tools described in the [[WebFund 2015W: Tutorial 2|Tutorial 2]].

In this tutorial you should do the following:
* Get [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/session-demo.zip session-demo] running.
* Try logging in to the app using two different browsers (e.g., Firefox and Chrome). What happens when you logout from one browser - how does it affect the other?
* Observe the request and response for the app's home page (http://localhost:3000). Look at both the network panel (load the page ''after'' selecting the network panel) and the HTML DOM view (Inspector/Elements)
* Observe the contents of the form submit POST request: how much data is sent to the server? Observe it both from the browser side (to see what is sent) and inside of node, particularly where the POST results are returned.
* The session state is stored in the browser. Can you figure out the user's username from this information?
* What does the req.body and req.session look like just before a page gets rendered?

To get checked off, show a TA the following:
* A session cookie sent by the browser
* A session cookie stored on the server

Questions to ponder:
* Who can observe the cookie? Modify it?
* How "persistent" are sessions on the server? The client?
* How could you "hijack" a session? Does the difficulty of session hijacking relate to whether a login is password protected or not?
* How much code would you have to add to [[WebFund 2015W: Tutorial 3|tinywebserver]] in order to get it to duplicate the functionality of session-demo?