Use RFC6265 rules for cookie path & path matching
authorShane Kearns <ext-shane.2.kearns@nokia.com>
Fri, 8 Jun 2012 13:56:11 +0000 (14:56 +0100)
committerQt by Nokia <qt-info@nokia.com>
Tue, 26 Jun 2012 22:46:35 +0000 (00:46 +0200)
commit058fddd1c01d49ee9fe8b70587a088d73f2c8e3c
treefc732f423b90b0721a9596048c6369f2fabcca3e
parentd76bd0d7358b1c061f3c685a9256243eb9f11d7a
Use RFC6265 rules for cookie path & path matching

Url encoding of paths is no longer used. This matches the
current release behaviour of Firefox, Chrome and MSIE browsers.
RFC6265 does not allow this type of encoding.

This fixes remaining path test cases in the IETF test suite.
Currently the path0027 test is passed by Firefox but failed by
Chrome and MSIE, so there is a potential compatibility issue.
However it is a corner case with a malformed cookie.

Task-number: QTBUG-15794
Change-Id: I9b02bb5adc32d614f512d314d06f2c60894aa2b0
Reviewed-by: Richard J. Moore <rich@kde.org>
src/network/access/qnetworkcookie.cpp
src/network/access/qnetworkcookiejar.cpp
tests/auto/network/access/qnetworkcookie/tst_qnetworkcookie.cpp