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
<VirtualHost *:80>
RewriteEngine On
RewriteCond%{REQUEST_URI}!^/\.well\-known/acme\-challenge/RewriteRule^(.*)$https://%{HTTP_HOST}$1[R=301,L]
</VirtualHost>
This results in a URL such as: http://example.com/cgi/home?screen=EPrint%3A%3AView&id=1234
being rewritten as: https://example.com/cgi/home?screen=EPrint%253A%253AView&id=1234
Using the 'NE (No Escape)' flag on the rewrite rule resolves this issue for my set-up at least: RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,NE,L]
It may not be as simple as this though - there have been changes in the way Apache/mod_rewrite handled the rewrites over time, and the 'NE' flag might break other aspects of the URL in older Apache versions (<2.4.1?):
Having deployed the suggested configuration from: https://ssl-config.mozilla.org/#server=apache&version=2.4.6&config=intermediate&openssl=1.0.2k-fips&ocsp=false&guideline=5.6 to a server, I experience double-encoded query-string issue.
This results in a URL such as:
http://example.com/cgi/home?screen=EPrint%3A%3AView&id=1234
being rewritten as:
https://example.com/cgi/home?screen=EPrint%253A%253AView&id=1234
Using the 'NE (No Escape)' flag on the rewrite rule resolves this issue for my set-up at least:
RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,NE,L]
It may not be as simple as this though - there have been changes in the way Apache/mod_rewrite handled the rewrites over time, and the 'NE' flag might break other aspects of the URL in older Apache versions (<2.4.1?):
The text was updated successfully, but these errors were encountered: