Apache Rewrite - Revision history

Michael.mast: /* No Encoding */

2019-04-15T17:55:22Z

No Encoding

Michael.mast: /* No Encoding */

2019-04-15T17:54:18Z

No Encoding

Michael.mast: /* No Encoding */

2019-04-15T17:54:06Z

No Encoding

Michael.mast at 17:53, 15 April 2019

2019-04-15T17:53:48Z

Michael.mast: Created page with "http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html I was scratching my head as to why %2 was being turned into %252 after a migration from one..."

2018-06-29T22:29:37Z

Created page with "<ref>http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html</ref> I was scratching my head as to why %2 was being turned into %252 after a migration from one..."

New page

<ref>http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html</ref> I was scratching my head as to why %2 was being turned into %252 after a migration from one vhost to another. Found out I needed to add [NE] to the rewrite rule in order for the slashed to be registered correctly.

← Older revision		Revision as of 17:55, 15 April 2019
Line 5:		Line 5:
	<ref>http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html</ref> I was scratching my head as to why %2 was being turned into %252 after a migration from one vhost to		<ref>http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html</ref> I was scratching my head as to why %2 was being turned into %252 after a migration from one vhost to
	another. Found out I needed to add [NE] to the rewrite rule in order for the slashed to be registered correctly.		another. Found out I needed to add [NE] to the rewrite rule in order for the slashed to be registered correctly.
		+	<br>
		+	<pre>
		+	<VirtualHost *:80>
		+	RewriteEngine On
		+	RewriteCond %{HTTPS} off
		+	RewriteRule ^/(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [NE]
		+	</VirtualHost>
		+	</pre>

@@ Line 1: / Line 1: @@
 ==No Encoding==
-<ref>https://httpd.apache.org/docs/current/rewrite/flags.html<ref>While working with nextcloud, I ran into a rewrite rule that would not keep slashes as I needed them. This was caused by the slashed being converted in a browser, then someone copying the converted URL as a link in another site.
+<ref>https://httpd.apache.org/docs/current/rewrite/flags.html</ref>While working with nextcloud, I ran into a rewrite rule that would not keep slashes as I needed them. This was caused by the slashed being converted in a browser, then someone copying the converted URL as a link in another site.
 <br>
 <br>
 <ref>http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html</ref> I was scratching my head as to why %2 was being turned into %252 after a migration from one vhost to
 another. Found out I needed to add [NE] to the rewrite rule in order for the slashed to be registered correctly.

@@ Line 1: / Line 1: @@
 ==No Encoding==
-While working with nextcloud, I ran into a rewrite rule that would not keep slashes as I needed them. This was caused by the slashed being converted in a browser, then someone copying the converted URL as a link in another site.
+<ref>https://httpd.apache.org/docs/current/rewrite/flags.html<ref>While working with nextcloud, I ran into a rewrite rule that would not keep slashes as I needed them. This was caused by the slashed being converted in a browser, then someone copying the converted URL as a link in another site.
 <br>
 <br>
 <ref>http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html</ref> I was scratching my head as to why %2 was being turned into %252 after a migration from one vhost to
 another. Found out I needed to add [NE] to the rewrite rule in order for the slashed to be registered correctly.

← Older revision		Revision as of 17:53, 15 April 2019
Line 1:		Line 1:
−	<ref>http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html</ref> I was scratching my head as to why %2 was being turned into %252 after a migration from one vhost to another. Found out I needed to add [NE] to the rewrite rule in order for the slashed to be registered correctly.	+	==No Encoding==
		+	While working with nextcloud, I ran into a rewrite rule that would not keep slashes as I needed them. This was caused by the slashed being converted in a browser, then someone copying the converted URL as a link in another site.
		+	<br>
		+	<br>
		+	<ref>http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html</ref> I was scratching my head as to why %2 was being turned into %252 after a migration from one vhost to
		+	another. Found out I needed to add [NE] to the rewrite rule in order for the slashed to be registered correctly.