Re: don't use POST for big GET [was: Dictionaries in HTML ]

>(B) Except for issue #6, I see no problem with moving towards
>the use of POST for queries, especially those that are too large
>for encoding in GET URLs, or those with non-URL character sets.

I still do not feel comfortable with this. Servers do not currently
implement the full HTTP protocol, which allows GET to have bodies, and
we use this as an excuse for not requiring them to do do. On the other
hand, you are proposing a new method, that would require many/most
servers to be changed. It seems to me that it would be easier, and
cleaner, in terms of implementation, to simply allow GET to have a
body (ie. parameterised GET). Caching can be controlled via headers,
and by extending your algorithm like this:

        if method == GET {
            if URL does not contain "?" then
                go up the cache hierarchy
	    if there is no body then
                go up the cache hierarchy
       bypass the cache hierarchy

Received on Tuesday, 6 February 1996 06:35:47 UTC