W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 1997

Re: Parsing requests

From: Dave Makower <davemak@pencom.com>
Date: Thu, 23 Jan 1997 13:43:50 -0500
Message-Id: <l03010d03af0d60264c6d@[192.168.112.81]>
To: Jigsaw Mailing List <www-jigsaw@www10.w3.org>
>I think all this is correct, I am right in assuming that if I add the
>query string when relocating (on a container resource), you're problem
>is solved ?

Only if the problem in parsing the URL (with trailing slash and query
string) is independently solved.

In case my meaning is not clear:

1) The browser requests
http://myserver.me.com/some_container?param1=value1&param2=value2

2) If the relocate part is fixed, then the server will send a reply
indicating that the correct URL is
http://myserver.me.com/some_container/?param1=value1&param2=value2

3) The browser then requests that URL, which still requires that the server
be able to parse the second URL correctly.  This is the most important
problem to solve.  The relocate problem is more a matter of convenience.



+---------------------+-------------------------+---------------------+
|    Dave Makower     |    davemak@pencom.com   |   WWW Specialist    |
+---------------------+-------------------------+---------------------+
|     Co-author of "Java Programming Basics" (Henry Holt/MIS:Press)   |
|                 http://www.pencom.com/javabasics/                   |
+----------------------------------+----------------------------------+
|   Pencom Web Works               |   (212) 513-7777   voice         |
|   Pencom Systems Inc.            |   (212) 513-1975   fax           |
|   40 Fulton St.                  |                                  |
|   New York, NY  10038            |   http://www.pencom.com/         |
+----------------------------------+----------------------------------+
Received on Thursday, 23 January 1997 13:43:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:25 GMT