|
Re: OT: POST v GET bandwidth?
by perrin (Chancellor) on Feb 08, 2008 at 16:32 UTC
|
I think the translation is "I don't understand HTTP and I think that the data arrives by magic when you use POST." | [reply] |
Re: OT: POST v GET bandwidth?
by samtregar (Abbot) on Feb 08, 2008 at 17:32 UTC
|
I believe the POST in the message refers to the US Postal Service. You should print out your data and mail it in.
-sam
| [reply] |
Re: OT: POST v GET bandwidth?
by moritz (Cardinal) on Feb 08, 2008 at 16:16 UTC
|
The only connection I can think of is URL encoding.
For non-ASCII chars and "special" chars you need three bytes per data byte (think %20).
But since the length of an URL is quite limited, I don't think it really matters.
| [reply] |
Re: OT: POST v GET bandwidth?
by Gavin (Archbishop) on Feb 08, 2008 at 17:59 UTC
|
HTTP GET is designed so that all information necessary for the interaction is part of the URI, thus promoting URI addressability. With HTTP POST, some information intended to affect change to the resource state may be part of the protocol headers, not in the URI. With this approach, the resulting URI for identifying the resource may be shorter, but the advantages of URI addressability are lost.
As already mentioned by moritz the difference in size is unlikely to make much difference to bandwidth.
From
W3Org
| [reply] |
Re: OT: POST v GET bandwidth?
by ikegami (Patriarch) on Feb 08, 2008 at 17:55 UTC
|
URI escaping used by GET request is quite expensive. POST request can can use different escaping mechanism and compress the data, so it should be smaller, if anything.
There is caching difference between GET and POST, but caching is probably not involved here.
| [reply] |
|
|
The form in question is about half way down this page, and it only takes 2 10-digit integer arguments. Not much scope for compression there.
The stupid bit is that if you use the form on that page, which submits it using a POST request, it still requests "Please use POST instead of GET. I have limited bandwidth."... so I think perrin hit the nail on the head.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
Re: OT: POST v GET bandwidth?
by chromatic (Archbishop) on Feb 08, 2008 at 19:21 UTC
|
POST requests are more difficult to link from another web site by just copying and pasting a URI into HTML. They're not much more difficult, however.
| [reply] |
Re: OT: POST v GET bandwidth?
by dsheroh (Monsignor) on Feb 08, 2008 at 22:19 UTC
|
Perhaps his web logs are being written over the network to a shared drive (or maybe even a syslog server) and he's concerned about the impact on LAN bandwidth consumption if he has to log longer URIs for GET requests?
(Yeah, it's a stretch, but it's the best I could come up with...) | [reply] |