Open Bug 1898891 Opened 1 year ago Updated 1 year ago

Move captive portal detection to an endpoint that returns 204

Categories

(Core :: Networking, enhancement, P3)

Product:
Core
Component:
Networking
Type:
enhancement

Tracking

()

People

(Reporter: valentin, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

WIP: Bug 1898891 - See if 204 captive portal endpoint works better r=#necko
48 bytes, text/x-phabricator-request
Details | Review

(In reply to tim from bug 1887714 comment #15)

I tried both of those builds and both seem to work with no captive portal detection.

It seems an endpoint that responds with a 204 status would generate fewer false positives.
We should investigate how easy that is to achieve on the server-side.

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

Attachment

General

Creator:
Created:
Updated:
Size: