Bug 97077 - Different treatment of HTTP-EQUIV metas and HTTP headers
Summary: Different treatment of HTTP-EQUIV metas and HTTP headers
Status: RESOLVED REMIND
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-15 15:52 UTC by Eckhart Wörner
Modified: 2008-05-06 10:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Frameset for the HTTP header (355 bytes, text/html)
2005-01-15 15:58 UTC, Eckhart Wörner
Details
Frameset for the HTTP-EQUIV meta (357 bytes, text/html)
2005-01-15 16:17 UTC, Eckhart Wörner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eckhart Wörner 2005-01-15 15:52:07 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    SuSE RPMs
OS:                Linux

In HTML, you can specify meta tags that should work similarly to headers that are sent within HTTP.

The following pages show this:
http://www.ewsoftware.de/temp/cookie-test.php
http://www.ewsoftware.de/temp/cookie-test.html

The first page requests a cookie via HTTP, the second one requests a cookie via a <meta /> tag.
Both URLs try to set the same cookie.

To show the difference between the two methods:
1. Create a first local html file with a frameset containing one frame with the first URL in it.
2. Create a second local html file with a frameset containing one frame with the second URL in it.
3. Show both files in konqueror.

You will see that the second frameset shows a request for a cookie, the first one does not.

Expected behaviour:
a) Both local files raise a dialogue that asks for a cookie to be set
or
b) none of them asks for a cookie to be set
Comment 1 Eckhart Wörner 2005-01-15 15:58:48 UTC
Created attachment 9105 [details]
Frameset for the HTTP header
Comment 2 Eckhart Wörner 2005-01-15 16:17:29 UTC
Created attachment 9106 [details]
Frameset for the HTTP-EQUIV meta
Comment 3 Eckhart Wörner 2005-01-15 16:35:04 UTC
Alternatively, you can use the two attachments to see the different behaviour.

There is no wrong behaviour if you put both frameset and frame page to the same domain.
Comment 4 Thiago Macieira 2005-01-17 02:43:59 UTC
Both attachments are identical.

You cannot set Cookies with HTTP headers without an HTTP server -- that it'll never work with local files.

Aside from that, I understand what the issue is.
Comment 5 Eckhart Wörner 2005-01-17 10:47:34 UTC
The attachments are not identical. They are framesets that frame different URLs (watch the ending).
And the cookies are not set within the frameset attachments but within the files they frame. And these files are on an http server.

Eckhart
Comment 6 J Appel 2006-09-12 13:46:58 UTC
the attachments are missing. Eckhart, do you experience this behaviour with kde 3.5.4? if yes, can you provide a testcase?
Comment 7 Eckhart Wörner 2006-09-12 22:22:45 UTC
The attachments are not missing, it's the files they refer to that were missing. I restored them. The behaviour is still there in 3.5.4.

To reproduce:
1. Set your Konqueror so that it asks for cookies.
2. Open http://bugs.kde.org/attachment.cgi?id=9106&action=view . You have to confirm a cookie. Reason: The contained frame page asks for a cookie via meta tag.
3. Open http://bugs.kde.org/attachment.cgi?id=9105&action=view . There is no cookie dialog for this page. If you open the contained frame page in its own window, you will see the dialog though.
Comment 8 J Appel 2006-09-13 12:37:34 UTC
Konqueror 3.5.4 and firefox 1.5.0.5 dont set a cookie as described in step 3 above. calling the frame page in a single window makes konqueror set the cookie, firefox doesnt.
Comment 9 Georges 2008-04-06 22:59:08 UTC
The files on the remote server are missing.
Could you please verify whether the bug is still present in a recent konqueror version ?

If possible please attache those two referenced files so one can test this without you having to host the files... :-)
Comment 10 George Goldberg 2008-05-06 10:02:56 UTC
Please reopen this bug if I testcase or example of the bug that is still reachable can be provided.