Jump to content

Talk:HTTP

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Gamernotnerd (talk | contribs) at 01:46, 19 March 2008. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The {{GAN}} template should be substituted at the top of the article talk page.

HTTP is 8-bit clean

mkvlnfdmbjknjkmcbvjhzcbnlikz/bdnhjkvis a 7-bit protocol and uses MIME encoding, here is an excerpt from RFC 2068 which makes it clear that HTTP is not a 7-bit protocol:

3.6 Transfer Codings



Transfer coding values are used to indicate an encoding transformation that has been, can be, or may need to be applied to an entity-body in order to ensure "safe transport" through the network. This differs from a content coding in that the transfer coding is a property of the message, not of the original entity.

transfer-coding = "chunked" | transfer-extension transfer-extension = token

All transfer-coding values are case-insensitive. HTTP/1.1 uses transfer coding values in the Transfer-Encoding header field (section 14.40).

Transfer codings are analogous to the Content-Transfer-Encoding values of MIME , which were designed to enable safe transport of binary data over a 7-bit transport service. However, safe transport has a different focus for an 8bit-clean transfer protocol. In HTTP, the only unsafe characteristic of message-bodies is the difficulty in determining the exact body length (section 7.2.2), or the desire to encrypt data over a shared transport.

-- The Anome 09:18, 5 March 2002 (UTC)[reply]

Above remark isn't dated. I'll date stamp so when this is old, the next sad guy with a broom knows they can safely delete it. --BozMo 10:26, 23 May 2004 (UTC)[reply]

GET, PUT, POST, DELETE

It'd be nice if there were notes on GET, PUT, POST, DELETE, and what they look like when sent. --LionKimbro - 03 Jul 2004

It also has aids, and is to be nice if PROPFIND were listed. I'm having trouble finding out what it means. OPTIONS is another that is omitted.

Protocol leadership

The statement in the article that HTTP is being maintained by W3C is incorrect, see http://www.w3.org/Protocols/. Their architecture team hasn't had anything to do with it since 2000. To my surprise, there seems to be no IETF activity either - the workgroup was concluded Oct. 2000. Does anybody know what the standardization status is? Yaron 21:59, Jul 12, 2004 (UTC)

HTTP/1.1 is considered a stable, working protocol, and resources are currently thought to be better sent elsewhere? BG 03:07, 8 January 2006 (UTC)[reply]
As of Oct 2007, there's a new IETF working group: HTTPbis. This should probably be mentioned in the main article. Reschke (talk) 13:08, 15 December 2007 (UTC)[reply]

URL = Uniform or Universal? URL page shows both

Uniform Resource Locator shows up twice on this page, yet the URL page itself uses Uniform in the title, then Universal in the first sentence, which is right? 41222-KenS —Preceding unsigned comment added by 192.31.106.36 (talk) 17:49, 22 December 2004

Universal was renamed to Uniform, but is still in common use. See http://www.ietf.org/rfc/rfc2396.txt (uniform) and http://www.ietf.org/rfc/rfc1630.txt (universal) (david)150.101.166.15 00:40, 19 March 2007 (UTC)[reply]

More samples

Please add a sample POST request. —Preceding unsigned comment added by Njh@bandsman.co.uk (talk • contribs) 10:36, 4 October 2005

Here is the requested sample, would somebody integrate it to the article if deemed useful. Also, I'm not sure how to read the GET sample. Like the response, the request too is followed by a single blank line. So yes, there are two consencutive newlines, but only a single blank line. Does the current wording make this clear?

The following example request uses the POST request method to send information entered by the user to a web form:

Client request, using POST (the line starting username= is not followed with a newline) 

POST /login.php HTTP/1.1
Host: www.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: 36

username=john.smith&password=secret1

Responses to POST requests are usually similar to responses to GET requests. However, in the following sample response the server uses the 303 See Other status code to make the client follow up with a GET request to the specified location:

Server response, using status code 303 

HTTP/1.1 303 See Other
Location: http://www.tania-handicraft.com/login_failed.php

Aapo Laitinen 21:12, 24 October 2005 (UTC)[reply]

For large POSTs the body text (or data) often does not arrive in one go. It would be nice to show how the recipient of the POST data knows when all data has arrived. Shinobu 14:24, 2 January 2007 (UTC)[reply]

I have submitted the article HTTP cookie for peer review (I am posting this notice here as this article is related). Comments are welcome here: Wikipedia:Peer review/HTTP cookie/archive1. Thanks. - Liberatore(T) 16:57, 14 January 2006 (UTC)[reply]

Is "delimition" actually a real word?

In the "HTTP connection persistence" section, the article states "There is a HTTP/1.0 extension for connection persistence, but its utility is limited due to HTTP/1.0's lack of unambiguous message delimition rules".

Is "delimition" really a word? Maybe it should read "... lack of unambiguous rules for delimiting messages" -- —Preceding unsigned comment added by 69.231.218.177 (talk) 00:18, 22 January 2006

I was wondering about that too. I fixed it. Catamorphism 06:50, 22 January 2006 (UTC)[reply]

Page title

This page is currently at HyperText Transfer Protocol which seems to be an odd title since I don't see why it should be capitlized this way. I checked RFC 2616, w3c and did a google search. The Google search revealed that some indeed use thsis capitalisation but that the official sources don't. To me this use of camel case seems unjustified. But since so many use this capitalization I wonder why? Jeltz talk 14:38, 20 April 2006 (UTC)[reply]

I agree. The same thing happened with XML, where people wanted to write the language name as eXtensible Markup Language in order to "explain" the initialism. I feel the page title of this article should be Hypertext Transfer Protocol because that's what HTTP stands for. HTTP != H.T.T.P.—mjb 18:15, 20 April 2006 (UTC)[reply]
I have put this page on requested moves now. Jeltz talk 09:42, 25 April 2006 (UTC)[reply]
I have requested a move from HyperText Transfer Protocol to Hypertext Transfer Protocol. Jeltz talk 09:42, 25 April 2006 (UTC)[reply]
Done. —Nightstallion (?) Seen this already? 15:27, 1 May 2006 (UTC)[reply]

Additional page regarding HTTP Headers

I suspect this question comes mostly from my inability to search, but I figure I'll ask it anyway. I've tried looking, but can't seem to find one, so I'll ask here: is there a comprehensive list of HTTP headers on Wikipedia that's available? For example, an indepth list of the header commands such as Host, Content-Type, Connection, etc. I realize, of course, that they're in the RFC2616 specs, but I'd like to know if there's one on Wikipedia. If there isn't, I'll most certainly make one. verix 00:00, 5 August 2006 (UTC)[reply]

1999? HTTP 1.1 vs 1.0?

People considering using name-based shared IP hosting need date/time context info -- need to know when the transition to supporting this feature happened in the real world. Which versions of which browsers do and don't support this feature? What other software that still might be in use does not support this feature? Since 1.1 was last issued in 1999, it seems like we can assume that all major software issued after that has the feature. But the feature was optional at least for some years previous? When did the feature first come into general use, on what software? Is there an easy way to test a piece of software to see if it supports this feature? 69.87.203.196 12:27, 11 January 2007 (UTC)[reply]

Persistent connections in 1.0?

I can't find something about that in the RFC. AFAIK this was introduces in 1.1 --87.230.112.22 15:07, 9 February 2007 (UTC)[reply]

History

Seems strange that this page doesn't have a "history" section like so many other wikipedia pages about specific technologies. Tim Berners-Lee is only mentioned in a link at the bottom! —Preceding unsigned comment added by 139.133.7.38 (talk) 10:20, 7 March 2007

I agree, the WorldWideWeb article states that Tim invented HTTP years before the first browser, prompting me to wonder what he could have been using HTTP for. The version history section is immensely insufficient. 207.177.231.9 11:26, 16 August 2007 (UTC)[reply]

GET, PUT, POST

Perhaps a note that PUT is not supported by any common Web browser? (You can put a HTTP method on a form or entity, but unless the method is POST, your web browser will send a GET message). (david)150.101.166.15 01:17, 19 March 2007 (UTC)[reply]

This article is unreadable.

This is no way to write an explanatory article on a technological topic, it introduces way too many concepts with little clarification and is actually directed at people with prior knowledge of what http is. There's too much detail that links elsewhere, and in order for someone to grasp the contents of this article they should keep reading the links instead of the article itself. Please don't introduce concepts if you don't know how to explain them. Simplicity is the best way, albeit the hardest to write. Some wikipedians might well be educated and commited to the encyclopedia but they are no educators that's for sure. It's a shame... 91.140.40.243 15:16, 28 April 2007 (UTC)[reply]

True. I've tagged the talk page. Chris Cunningham 19:24, 28 April 2007 (UTC)[reply]

www.bpn.go.id

gamana caranya pendaftaran di STPN? —The preceding unsigned comment was added by 69.88.4.109 (talk) 04:45, 2 May 2007 (UTC).[reply]

urls do not necessarily map to dirs and files.

>Request line, such as GET /images/logo.gif HTTP/1.1, which >requests the file logo.gif from the /images directory

is in the article but "/images/logo.gif" is actually just a string that does not mean that logo.gif is inside the directory "images" nor that a directory "images" exists - and it could still be a 200-response. I know, this is not really important to understand what http is but I feel that a lot of people get that wrong and it might help someone trying to learn about http to give correct information on this issue (maybe even mentioning apache's mod_rewrite if that's not too far off). I'd suggest some text but my english is too bad for encyclopedic usage. 213.39.156.159 20:03, 1 June 2007 (UTC) --200.144.26.31 19:27, 9 October 2007 (UTC)[reply]

HTTP 1.2?

I've written an article about where I see HTTP heading. It's called HTTP 1.2 -- What it needs. If anyone thinks it's relevant, and wants to post this on the article page (maybe in an "External links" section), that would be great (I'm not allowed to because I wrote the article).

-- TimNelson (talk) 05:14, 18 December 2007 (UTC)[reply]

why am i being brought here?

I am getting a weird error. When i put this address into the address bar, http//www.softimage.com/products/xsi/video_tour/default.aspx it is bringing me to the wiki on http. Can anyone else confirm this? Softimage has nothing to do with wikipedia. Its like the address bar is ignoring everything after the http and searching just that. Any thoughts anyone? —Preceding unsigned comment added by 64.180.74.129 (talk) 18:09, 16 February 2008 (UTC)[reply]

You're missing the ":" in that address - it should be "http://", not "http//"; presumably your browser is then getting confused by the "//", searching for just the "http" part, and bringing you to the first result - this Wikipedia page. Hope that helps! - IMSoP (talk) 18:38, 16 February 2008 (UTC)[reply]

Hello Rebecca, how are you today? —Preceding unsigned comment added by 205.202.240.41 (talk) 19:08, 13 March 2008 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:HTTP&oldid=199243231"