What hidden features of HTTP do you think are worth mentioning?
By hidden features I mean features that already are part of the standard but widely rather unknown or unused.
Just one feature per answer please.
What hidden features of HTTP do you think are worth mentioning?
By hidden features I mean features that already are part of the standard but widely rather unknown or unused.
Just one feature per answer please.
The protocol allows you to define your own custom-fields. These can be used to carry other information if you don't want to use cookies for it.
The fact that referrer was misspelled and it was decided that the misspelling should be kept.
204 No Content
I thought 204 was just if you have no content to display, but the spec looks like there is additional behavior that the user agent "not change its document view."
According to HOWTO: Configure Apache to Return a HTTP 204 (No Content) for AJAX
Also, 204 No Content proposes this is a good technique for "web bugs" or "beacons" if you want to save on every last byte of network traffic you can.
Have anyone ever seen 402 Payment Required?
Status codes :
http://www.domain.invalid/index.php?id=44
is called, if the query (id=44
) couldn't return ressource, why not return a status code404
?http://www.domain.invalid/index.php?id=foo
is called whereasid
only accepts integers, why not return a status code400
?200
(ok, no problem, you do it well) instade of401
?Yes, status codes seems to be a kind of secret functionality of HTTP to some web developers... But I wonder if the most occult of all the "features" of this protocol isn't its RFC!
Response Code
410 Gone
:Web spiders (most notably Google) will de-index (typically on next crawl) a page which starts returning 410.