Use a separate cookie jar for search suggestions

RESOLVED FIXED

Status

()

Firefox for iOS
General
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: rnewman, Assigned: jhugman)

Tracking

unspecified
All
iOS

Firefox Tracking Flags

(fxios1.1+)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Stefan pointed this out last week: we should make sure that our search suggestions don't use the same pools as our browsers, lest we accidentally send up your Google cookie etc.

This bug might be closed because we already do the right thing, so let's investigate.
(Reporter)

Updated

3 years ago
tracking-fxios: ? → 1.1+
(Assignee)

Updated

3 years ago
Assignee: nobody → jhugman
(Assignee)

Comment 1

3 years ago
Created attachment 8658639 [details] [review]
Use a separate Alamofire.Manager for search suggestions.

Switched to using the ephemeral configuration, which definitely will be a different config to the WKWebView.

It isn't clear if this is definitively the right thing to do: search engine settings, e.g. safe search would be a counter example.
Attachment #8658639 - Flags: review?(rnewman)
Attachment #8658639 - Flags: review?(etoop)
(Assignee)

Updated

3 years ago
Status: NEW → ASSIGNED
(Reporter)

Updated

3 years ago
Attachment #8658639 - Flags: review?(rnewman) → review+
Attachment #8658639 - Flags: review?(etoop) → review+
(Assignee)

Updated

3 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.