Bug 186448

Summary:	Setting a cookie on a 302 response is not taken into account
Product:	WebKit	Reporter:	youenn fablet <youennf>
Component:	Page Loading	Assignee:	Nobody <webkit-unassigned>
Status:	NEW
Severity:	Normal	CC:	beidson, cdumez, ggaren, nicolasd, sihui_liu, webkit-bug-importer, youennf
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified

youenn fablet

Reported 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.

Attachments
Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2018-06-08 15:13:33 PDT

<rdar://problem/40952671>

Nicolas D

Comment 2 2018-10-24 01:20:51 PDT

We have the exact same issue. Did you find any workaround ?

Note You need to log in before you can comment on or make changes to this bug.