Bug 52077
| Summary: | [Qt] QtWebKit always supports cookies | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Benjamin Poulain <benjamin> |
| Component: | New Bugs | Assignee: | Benjamin Poulain <benjamin> |
| Status: | RESOLVED INVALID | ||
| Severity: | Trivial | Keywords: | Qt, QtTriaged |
| Priority: | P5 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | |||
| Bug Blocks: | 52081 | ||
Benjamin Poulain
The function bool cookiesEnabled(const Document* document) does not actually need to check anything, it is not possible to disable cookies with Qt.
Checking for the cookie jar was useless because one is created on the fly is none is set:
QNetworkCookieJar *QNetworkAccessManager::cookieJar() const
{
Q_D(const QNetworkAccessManager);
if (!d->cookieJar)
d->createCookieJar();
return d->cookieJar;
}
Checking for the network access manager is not useful for the same reason.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Benjamin Poulain
Invalid. I realised my mistake while doing the autotest.
QNetworkAccessManagerPrivate::createCookieJar() creates the jar only once. You can set a null cookie jar and the current implementation of cookiesEnabled() is incorrect.
Follow up bug report soon.