Which utc during daylight saving time and utc otherwise
PdTHT Request
OBTENIR / PdTHT/1.0
Dernière-modification: Yb-9-A A:z:p
Type-de-contenu: text/plain
Dates/times are specified using an ISO8601-like format, except that numbers are represented in sexagesimal, as above. So a date is written as YY-M-D H:M:S. The server implicitly uses the Paris time zone, which is UTC+2 during Daylight Saving time and UTC+1 otherwise. (Conveniently for you, DST does not end until after this assignment is over.) So the due date of the assignment, which in HTTP would be represented as Wed, 05 Oct 2016 16:30:00 GMT, would be written as Yb-A-5 I:V:0, and the date in the example above is actually September 10, 2016 at 10:59:49.
Proxy Protocol
...
The proxy is then responsible for contacting the site cs438.fr and requesting the file /index.html. It should pass along any headers to the web server and then return the result back, translating appropriate headers. (Any headers not listed in the glossary below should be passed on untranslated.) The one exception is the Connection: header: the browser uses this header to specify whether the connection to the proxy should be kept open or not, whereas the Connexion: header sent to the web server should govern whether the connection from the proxy to the web server should be kept alive or closed.
Cut-through Forwarding
To submit the code, please check the code into subversion. Please use the URL https://subversion.engr.illinois.edu/svn/fa16-ece438/NETID/mp1, where NETIDshould be replaced by your own NetID, unless we have set up a group project for you. We will grade the revision closest to the deadline, unless you explicitly ask us to grade an earlier or later revision. The course late policy applies: you will lose 2% off your grade for every hour or portion thereof that your assignment is late. Exceptions to this late policy will be granted only in exceptional circumstances.
To collaborate with your partner, you can request for us to create a group directory for you in subversion; alternately, you can use the Engineering Gitlab server, but you will need to check your final submission into subversion. You may wish to learn about the git svn command to keep the subversion and git repositories in sync. If you prefer, you can use GitHub or BitBucket to store your code but make sure that you are using a private repository: putting your MP code inside a public repository is considered to be a facilitation of plagiarism and will be considered an academic integrity violation.
Glossary
| English | French | Description |
|---|---|---|
| Request methods | ||
| GET | OBTENIR | Get an object from the web server. A GET request has an empty message body. |
| POST | POSTER | Upload form data or a file to a website. The request will have a message body, with the length specified in the header. The response to a POST request should never be cached. |
| HEAD | TÊTE | Get the headers of the object, but not the object itself. Like a GET request but the response has an empty message body. HEAD requests can be satisfied from the cache. |
| HTTP headers | ||
| Host: | Hôte: | A required header in HTTP/1.1 (and PdTHT/1.0). Even though the request to the proxy has the host inside the request URL, it will also be duplicated inside the request. The value of this header should be passed unmodified to the server. |
| Content-Length: | Longeur-Contenu: | Length of the message body. Required when a message body is non-zero, unless chunked encoding is used. |
| Transfer-Encoding: chunked | Encodage-de-Transfert: en-morceaux | Chunked encoding allows the client or server to send a message body without specifying the length ahead of time. You can read the RFC specification of how chunked encoding works. PdTHT uses a similar encoding scheme but uses sexagesimal numbers for chunk sizes. E.g.: D 438 students! |
| Connection: close | Connexion: fermer | The connection should (if sent by a client)/will (if sent by a server) be closed after the next response is complete. |
| Cache-Control: | Contrôle-de-Cache: | Specification that is responsible for caching |
| Cache-Control: public | Contrôle-de-Cache: public | Content may be cached by a shared proxy |
| Cache-Control: private | Contrôle-de-Cache: privé | Content may only be cached by the browser |
| Cache-Control: no-cache | Contrôle-de-Cache: pas-de-cache | Content should not be cached. For our purposes, privé and pas-de-cache are similar, but you should translate it for the browser so that it can behave appropriately. |
| Cache-Control: max-age=... | Contrôle-de-Cache: âge-max=... | When sent by the server, how long an object may be cached before it must be revalidated. When sent by the client, the oldest cached version it will accept; if max-age=0 the proxy must revalidate even if the object has not yet expired. |
| Date | Date | Date that the request or response was generated. Should be passed between the server and client but translated to/from the french date format. |
| Last-Modified: | Dernière-Modification: | Date when the file being returned was last modified. |
| If-Modified-Since: | Si-Modifié-Depuis: | Validate whether the object has changed since the cached version; the date must be the same as returned in the Last-Modified header. The server will return a 304 response with an empty body if the file hasn't changed and a 200 response if it has. |
| Age: | Âge: | Seconds since the object has been validated. Usually this will only be sent by the proxy, but if the proxy receives this header from a server, this indicates that it is in a chain of proxies and it should use this as the initial age of the response in its cache (and pass it onto the client). |
| Vary: | Varier: | Normally you can use a cached object to respond to all requests with the same URL. A Varyheader specifies that the cached object depends on the value of the headers listed therein. For example, if the server specifies Vary: Accept, then the cached object should only be returned to clients that supply identical Accept headers. If a different header value is included in a request, the proxy must make a new request to the server with this new Accept header. It can then cache different versions of the object for each value of the Accept header it's seen. |
| Via: | Via: | This header must be added in both directions, with the value 1.1 proxyname (you can name your proxy whatever you want). If a Via header already exists, you should append your proxy name to it, as in: Via: 1.1 incomingproxy, 1.1 proxyname |
| Range | Gamme | This header specifies that the requester only wants a partial response. The value of the header is written as bytes=100-199 (octets=1f-3J), which requests 100 bytes starting with byte 100. (The first byte is numbered 0.) The server response contains the header Content-Range: 100-199/735 (Gamme-de-Contenu: 1f-3J/CF) which says that bytes 100-199 are included, out of a total of 735 bytes. Partial requests should be satisfied out of the cache if possible; if you need to go out to the server, you should forward a partial request to it. |
| Accept | Accepte | The value of these headers should be passed between the proxy and the server unmodified, you just need to translate the name. |
| Accept-Charset | Accepte-Carjeu | |
| Accept-Encoding | Accepte-Encodage | |
| Accept-Language | Accepte-Langue | |
| Content-Type | Type-de-Contenu | |
| Cookie | Biscuit | |
| Content-Enconding | Encodage-de-Contenu | |
| Content-Language | Langue-de-Contenu | |
| Location | Emplacement | |
| Server | Serveur | |
| Referer | Référenceur | |
| Set-Cookie: | Dêfinir-Biscut: | |
| User-Agent: | Agent-Utilisateur: | |