W3C home > Mailing lists > Public > www-talk@w3.org > March to April 1996

Re: www-talk-d Digest V96 #3

From: Laurence A. Bates <Laurence@msu.edu>
Date: Thu, 11 Apr 1996 14:38:59 -0500
Message-Id: <9604111858.AA23769@serv1.cl.msu.edu>
To: www-talk@w3.org
Microsoft's Internet Explorer does that automatically.

At 01:14 PM 4/11/96 -0400, you wrote:
>www-talk-d Digest				Volume 96 : Issue 3
>
>Today's Topics:
>	 Re: browsers
>	 HTTP protocol regarding form elements order
>	 Re: HTTP protocol regarding form elements order
>	  Re: HTTP protocol regarding form elements order
>	 Re: HTTP protocol regarding form elements order
>	  Re: HTTP protocol regarding form elements order
>	 GET HEAD to Proxy
>Date: Fri, 05 Apr 1996 14:08:02 +0100
>From: Martin Hamilton <martin@mrrl.lut.ac.uk>
>To: Penny Hix <hix@math.odu.edu>
>Cc: www-talk@w3.org
>Subject: Re: browsers
>Message-Id: <199604051308.OAA17935@gizmo.lut.ac.uk>
>Content-Type: text/plain; charset=us-ascii
>content-length: 1093
>
>Penny Hix writes:
>
>| Can anyone help me find out how a browser would go about filling in the
>| http:// part of a web address instead of the user having to type it in
>| for every web site they want to visit?  I am currently enrolled in an
>| internet course and have been given an assignment to find this out and
>| write an RFC. Any help would be tremendously appreciated.
>
>It's usually something along the lines of:
>
>  If the URL starts with a protocol scheme you know about,
>    e.g. "http", don't muck about with it
>  If the URL starts with
>    "gopher." -> prepend "gopher://"
>    "ftp." -> prepend "ftp://"
>    (maybe repeat for other protocol schemes you know about)
>  If you still don't have a URL which begins with a protocol
>    scheme you know about, prepend "http://"
>
>Russ Wright and I have been scribbling a little document about these
>site naming conventions, which seems to have been adopted by the IETF's
>Integrated Directory Services working group.  Should be coming out as
>an Internet Draft real soon now.  Too contentious to make it to RFC ?
>We'll see! ;-)
>
>Martin
>Date: Fri, 5 Apr 1996 12:26:27 -0500 (EST)
>From: Niranjan Ramakrishnan <niranjan@eecs.umich.edu>
>To: www-talk@w3.org
>Subject: HTTP protocol regarding form elements order
>Message-Id: <199604051726.MAA07221@wits-end.eecs.umich.edu>
>content-length: 877
>
>Hi,
>
>Sorry to disturb you guys but I'm pretty concerned about the HTTP specs
>regarding the order in which form input is returned to a cgi program. Is
>it *necessary* that the form elements should always be returned in the
>same order as they were present in the original HTML document? I need this
>info desperately as it would dictate the parsing methodology I use when I
>process input from a POST query.
>
>For eg if I have several input text fields say
>
><input type=text name=a>
><input type=text name=a>
><input type=text name=a>
>
>and the user enters for each in order b c and d, will HTTP require that
>the values returned to me would be of the form :
>
>a=b
>a=c
>a=d
>
>in that order?
>
>Thanks for putting up with this query? But I need the info pretty badly...
>
>Any help would be deeply appreciated.
>
>Sincerely,
>
>Niranjan Ramakrishnan
>Grad Student,
>University of Michigan, Ann Arbor
>Date: Fri, 5 Apr 1996 10:44:17 -0800 (PST)
>From: "Gregory J. Woodhouse" <gjw@wnetc.com>
>To: Niranjan Ramakrishnan <niranjan@eecs.umich.edu>
>Cc: www-talk@w3.org
>Subject: Re: HTTP protocol regarding form elements order
>Message-Id: <Pine.SGI.3.91.960405104225.14708B-100000@shellx.best.com>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>content-length: 1269
>
>On Fri, 5 Apr 1996, Niranjan Ramakrishnan wrote:
>
>No. The form elements can be returned in any order. For example,
>
>alpha=one&beta=two
>
>is treated as equivalent to
>
>beta=two&alpha=one
>
>> Hi,
>>
>> Sorry to disturb you guys but I'm pretty concerned about the HTTP specs
>> regarding the order in which form input is returned to a cgi program. Is
>> it *necessary* that the form elements should always be returned in the
>> same order as they were present in the original HTML document? I need this
>> info desperately as it would dictate the parsing methodology I use when I
>> process input from a POST query.
>>
>> For eg if I have several input text fields say
>>
>> <input type=text name=a>
>> <input type=text name=a>
>> <input type=text name=a>
>>
>> and the user enters for each in order b c and d, will HTTP require that
>> the values returned to me would be of the form :
>>
>> a=b
>> a=c
>> a=d
>>
>> in that order?
>>
>> Thanks for putting up with this query? But I need the info pretty badly...
>>
>> Any help would be deeply appreciated.
>>
>> Sincerely,
>>
>> Niranjan Ramakrishnan
>> Grad Student,
>> University of Michigan, Ann Arbor
>>
>
>---
>Gregory Woodhouse     gjw@wnetc.com
>home page:            http://www.wnetc.com/
>resource page:        http://www.wnetc.com/resource/
>Date: Fri, 5 Apr 1996 11:01:55 PST
>From: mwm@contessa.phone.net (Mike Meyer)
>To: www-talk@w3.org
>Subject:  Re: HTTP protocol regarding form elements order
>Message-Id: <19960405.749CC70.A5D5@contessa.phone.net>
>content-length: 415
>
>> No. The form elements can be returned in any order. For example,
>
>The HTML RFC (1866) disagrees with you. In particular, section 8.2.1
>(form submission for the mime type application/x-www-form-urlencoded
>say in point 2:
>
>        2. The fields are listed in the order they appear in the
>        document ...
>
>At least one major browser vendor got this wrong once, so I'd avoid depending
>on it if you can.
>
>	<mike
>Date: Fri, 5 Apr 1996 11:26:28 -0800 (PST)
>From: "Gregory J. Woodhouse" <gjw@wnetc.com>
>To: Mike Meyer <mwm@contessa.phone.net>
>Cc: www-talk@w3.org
>Subject: Re: HTTP protocol regarding form elements order
>Message-Id: <Pine.SGI.3.91.960405112024.4899B-100000@shellx.best.com>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>content-length: 912
>
>On Fri, 5 Apr 1996, Mike Meyer wrote:
>
>> > No. The form elements can be returned in any order. For example,
>>
>> The HTML RFC (1866) disagrees with you. In particular, section 8.2.1
>> (form submission for the mime type application/x-www-form-urlencoded
>> say in point 2:
>>
>>         2. The fields are listed in the order they appear in the
>>         document ...
>>
>> At least one major browser vendor got this wrong once, so I'd avoid depending
>> on it if you can.
>>
>> 	<mike
>>
>>
>Ah...I see what you mean. I wasn't actually aware that they were required
>to be returned in order.What I had in mind was that no information is
>lost by reordering the elements...but I guess I was making the tacit
>assumption that the NAME attributes would be unique to the form element.
>
>---
>Gregory Woodhouse     gjw@wnetc.com
>home page:            http://www.wnetc.com/
>resource page:        http://www.wnetc.com/resource/
>Date: Fri, 5 Apr 1996 12:29:17 PST
>From: mwm@contessa.phone.net (Mike Meyer)
>To: www-talk@w3.org
>Subject:  Re: HTTP protocol regarding form elements order
>Message-Id: <19960405.7593D88.B319@contessa.phone.net>
>content-length: 728
>
>> Ah...I see what you mean. I wasn't actually aware that they were required
>> to be returned in order.What I had in mind was that no information is
>> lost by reordering the elements...but I guess I was making the tacit
>> assumption that the NAME attributes would be unique to the form element.
>
>Well, you lose the information about what order the elements appeared
>in in the form, but that's usually fixed and known beforehand. I can
>imaging situations where it isn't, but not where it would matter.
>
>On the other hand, I have written code that had multiple occurences of
>the same NAME element, and depended on the order. I decided to rewrite
>it rather than depend on browsers to get this relatively minor point
>right.
>
>	<mike
>Date: Thu, 11 Apr 96 10:14:13 PDT
>From: jjames@firstfloor.com (John W. James)
>To: www-talk@w3.org
>Cc: ]@firstfloor.com
>Subject: GET HEAD to Proxy
>Message-Id: <9604111714.0D0584@james-hill-farm.firstfloor.COM.firstfloor.COM>
>content-length: 611
>
>Is a GET HEAD call supposed to work when a proxy is in use by
>the client? We had one caching proxy server that was returning
>a 500, but the server is in beta and I kind of dismissed this
>as the possible cause. I'm now seeing it at a customer's site,
>and that makes me think this might be something systemic.
>
>	John
>
>---------------------------------------------------------------
>John James                    Email:  jjames@firstfloor.COM
>First Floor, Inc.             Web:    http://www.firstfloor.COM
>444 Castro Street, Suite 200  Tel:    (415) 254-5101
>Mountain View. CA 94041       Fax:    (415) 968-1193
>
Received on Thursday, 11 April 1996 14:58:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:19 GMT