Skip to content
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.

Inefficient force-ssl detector #4

Open
yallxe opened this issue Dec 26, 2022 · 0 comments
Open

Inefficient force-ssl detector #4

yallxe opened this issue Dec 26, 2022 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@yallxe
Copy link
Owner

yallxe commented Dec 26, 2022

Websites may redirect twice or more, as in an example below

2022-12-26T21:12:41.253 [DEBUG] redirecting 'http://www.facebook.com/' to 'https://www.facebook.com/'
2022-12-26T21:12:41.254 [DEBUG] starting new connection: https://www.facebook.com/     
2022-12-26T21:12:41.256 [TRACE] registering event source with poller: token=Token(419430401), interests=READABLE | WRITABLE
2022-12-26T21:12:41.358 [TRACE] signal: Want
2022-12-26T21:12:41.358 [TRACE] signal found waiting giver, notifying
2022-12-26T21:12:41.358 [TRACE] poll_want: taker wants!
2022-12-26T21:12:41.501 [TRACE] signal: Want
2022-12-26T21:12:41.501 [TRACE] signal: Want
2022-12-26T21:12:41.502 [DEBUG] redirecting 'https://www.facebook.com/' to 'https://www.facebook.com/unsupportedbrowser'
2022-12-26T21:12:41.703 [INFO ] Forced HTTPS redirection detected: www.facebook.com

After first redirect, it was clear website have force-ssl enabled. Handling second redirect wasn't needed.

@yallxe yallxe added bug Something isn't working enhancement New feature or request labels Dec 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant