Transcript Assignment #5 - Extra Credit

Web Server Design
Assignment #5 Extra Credit
Old Dominion University
Department of Computer Science
CS 495/595 Spring 2010
Martin Klein <[email protected]>
In Addition to A5
• 5 points: Partial Gets
– implement all aspects of Partial GETs (week 6
lecture)
• 5 points: Implement “100 Continue”
response code
– see sections 8.2.3, 10.1.1, 14.20 of RFC-2616
– not implemented in Apache (as far as I can tell)
100 Continue
PUT /~mklein/cars/1966-Fairlane.txt
Host: coolfords.org
Date: Wed, 14 Apr 2010 04:34:00 GMT
Content-Type: text/plain
Content-Length: 193
Connection: close
PUT /~mklein/cars/1966-Fairlane.txt
Host: coolfords.org
Date: Wed, 14 Apr 2010 04:34:00 GMT
Content-Type: text/plain
Content-Length: 193
Connection: close
Expect: 100-Continue
______________
//
\\
---------//--------------\\------|
__
__
|
|--/ \--------------------/ \---|
\__/
\__/
HTTP 1.1 100 Continue
HTTP 1.1 201 Created
Date: Wed, 14 Apr 2010 04:34:00 GMT
Server: FordServer
ETag: “XYZ”
Connection: close
______________
//
\\
---------//--------------\\------|
__
__
|
|--/ \--------------------/ \---|
\__/
\__/
HTTP 1.1 201 Created
Date: Wed, 14 Apr 2010 04:34:00 GMT
Server: FordServer
ETag: “XYZ”
Connection: close
Possible response codes: 200, 201, 401, 403, 405, 411, 413, 414, 417
Applicable to any method in which the client sends an entity body to the server (i.e., POST, PUT)
Ignore the header if not applicable to the method.