You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @atauenis !
Since the version 0.15 I found that HTTPS proxies doesn't work for my setup anymore. In a few words:
HTTPS proxy server is set to XXX.XXX.XXX.XXX:8080 and perfectly available in my network. I have to mention HTTP proxy is set to the same XXX.XXX.XXX.XXX:8080 and works well.
Once I open SSL connection it fails like so:
When I disable HTTPS proxy it acts as expected:
I might miss something here, please advice.
~ Thanks
The text was updated successfully, but these errors were encountered:
None of WebOne versions were designed to work over true HTTPS. All are converting HTTP requests from old browsers to HTTPS connections to modern sites. It's strange that before the "Secure Web Proxy" option worked with WebOne. Probably you entered URL with HTTP://, not HTTPS://, and it opened via WebOne (same as if the Secure Proxy option is not set). If now the browser don't allow open osxdaily.com via HTTP (redirecting to HTTPS even before any network connection attempt), somewhy it added the domain to HSTS list.
I'm planning to implement real Secure HTTP support in some of future releases. This will be a very large work (needs rewriting ~50% of server code, including manual support for Keep-Alive and other difficult stuff over raw TCP sockets/Streams), but not impossible.
Hi @atauenis !
Since the version 0.15 I found that HTTPS proxies doesn't work for my setup anymore. In a few words:
HTTPS proxy server is set to XXX.XXX.XXX.XXX:8080 and perfectly available in my network. I have to mention HTTP proxy is set to the same XXX.XXX.XXX.XXX:8080 and works well.
Once I open SSL connection it fails like so:
When I disable HTTPS proxy it acts as expected:
I might miss something here, please advice.
~ Thanks
The text was updated successfully, but these errors were encountered: