Bug 186448 - Setting a cookie on a 302 response is not taken into account
Summary: Setting a cookie on a 302 response is not taken into account
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2018-06-08 15:13 PDT by youenn fablet
Modified: 2018-10-24 08:40 PDT (History)
7 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description youenn fablet 2018-06-08 15:13:16 PDT 
On a WKWebView, a request is sent and a 302 response is received with a Set-Cookie header.
When trying to access this cookie using the Cookie API, the cookie is not available.
Comment 1 Radar WebKit Bug Importer 2018-06-08 15:13:33 PDT 
<rdar://problem/40952671>
Comment 2 Nicolas D 2018-10-24 01:20:51 PDT 
We have the exact same issue. Did you find any workaround ?