[ee122] "full" URLs without Paths

[Simon Tan]

Should the client, given a URL without a 'Path' (?Path in the grammar),  
generate a valid GET request anyway? For example, if the client gets this  
on stdin:

http://localhost:7789

Should the client generate a GET request that looks like this:
GET / HTTP/1.0

... which is valid (and what I would assume). Or should it send a GET  
request that looks like this:
GET  HTTP/1.0

.. which results in the server saying "ERROR -- Invalid Absolute-Path  
token.", but is kinda logical if the grammar->GET translation is followed  
directly.

Note that if the user typed:
http://localhost:7789/

This problem would not occur, since the trailing '/' is passed into the  
GET string.


-- 
~Simon Tan >> undergraduate at UC Berkeley
Source: simtan at berkeley.edu