Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downgrade conn.internet.nl to same Request Path #1194

Closed
bwbroersma opened this issue Nov 21, 2023 · 0 comments · Fixed by #1195
Closed

Downgrade conn.internet.nl to same Request Path #1194

bwbroersma opened this issue Nov 21, 2023 · 0 comments · Fixed by #1195
Assignees
Labels
bug Unexpected or unwanted behaviour of current implementations

Comments

@bwbroersma
Copy link
Collaborator

Currently https://conn.internet.nl/connection/ downgrades to http://conn.internet.nl/, losing the Request Path, this might give problems with some browsers preferring a HTTPS request somehow. It seems more testing with HTTPS Upgrade / Strict HTTPS is needed, probably best to move to HTTPS soon, see:

Current problem:

$ curl -D- https://conn.internet.nl/connection/
HTTP/2 301
server: nginx
date: Tue, 21 Nov 2023 16:32:41 GMT
content-type: text/html
content-length: 162
location: http://conn.internet.nl
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
x-clacks-overhead: GNU Terry Pratchett
referrer-policy: same-origin
x-xss-protection: 1; mode=block
strict-transport-security: max-age=0;

<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
bwbroersma added a commit to bwbroersma/Internet.nl that referenced this issue Nov 21, 2023
@baknu baknu added the bug Unexpected or unwanted behaviour of current implementations label Nov 22, 2023
mxsasha pushed a commit that referenced this issue Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected or unwanted behaviour of current implementations
Development

Successfully merging a pull request may close this issue.

3 participants