[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#20810: Web site doesn't work in Konqueror
From:       Waldo Bastian <bastian () kde ! org>
Date:       2001-03-01 4:15:31
[Download RAW message or body]

On Thursday 22 February 2001 18:19, John Lindal wrote:
> Package: kcookiejar
> Version:
>
> Several people have reported to us that they are unable to complete the
> download process that begins at
> 
> https://stream.topchoice.com/cgi-bin/newplanetsoftware/demo/Code_Crusader_3
>.0.0_beta12_RH6.2.tgz?product_id=CC-3-0-BETA-12
>
> Since our web site works with Netscape, Mozilla, and IE, we have reason to
> believe that it is a bug in Konqueror rather than a problem with our web
> site.  (We are quite willing to make changes in our web site if it turns
> out that these other browser are simply being too lenient, however!)  We
> suspect that the problem results from our use of cookies because, after
> accepting the license and filling out the form that follows the license,
> cookies are set and an email is sent to the user.  However, when the user
> uses the links in the email message, the license is displayed as if no
> cookies had been set.
>
> The cookies names are strings like "Code_Crusader_3.0.0_beta12_RH6.2.tgz"
> and "Code_Crusader_3.0.0_beta12_RH6.2.rpm", while the values are strings of
> lower case letters.  The cookies are set to expire 3 days from the time
> when they were set.
>
> We realize that Konqueror is under heavy development, and that this may
> already have been fixed, or may be a known problem, but we decided that
> since the problem is clean and reproducible, it would at least make a good
> test.

Hi John,

The problem seems to be that you cookies haves spaces in their name.

I get the following header:

kio_http_debug: Got header (10666): "Set-cookie: Code Crusader 3.0.0 beta12 
(RH6.2)=1558018574191546543348164339954019911878"

And we send the follwoing header:
"Cookie: Code=1558018574191546543348164339954019911878"

which obviously isn't what you expect.
   
However I have little intent to fix that because the spec from  
http://www.netscape.com/newsref/std/cookie_spec.html does not allow spaces in
cookie names, nor does rfc2109.

http://www.netscape.com/newsref/std/cookie_spec.html  says
"Syntax of the Set-Cookie HTTP Response Header

This is the format a CGI script would use to add to the HTTP headers a new 
piece of data which is to be stored by the client
for later retrieval. 

Set-Cookie: NAME=VALUE; expires=DATE;
path=PATH; domain=DOMAIN_NAME; secure

NAME=VALUE
     This string is a sequence of characters excluding semi-colon, comma and 
white space. If there is a need to place
     such data in the name or value, some encoding method such as URL style 
%XX encoding is recommended, though no
     encoding is defined or required. "

So i would recommend to replace the spaces in your cookie name with either 
'%20' or with something like '_'.

Let me know if you want me to test something or if you encounter any other 
problem.

Cheers,
Waldo
-- 
bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com

[prev in list] [next in list] [prev in thread] [next in thread]