Re: Web: update documentation symlinks, and use https in RewriteRules (issue 551650043 by v.villen...@gmail.com)

2020-04-19 Thread v . villenave
Pushed as
https://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=b9255b50886e5e0de802a26fd486c908b0b55c0f

https://codereview.appspot.com/551650043/



Re: Web: update documentation symlinks, and use https in RewriteRules (issue 551650043 by v.villen...@gmail.com)

2020-04-11 Thread v . villenave
On 2020/04/09 19:52:47, c_sorensen wrote:
> I'm OK to have you push it, but I'd like to hear from those involved
in the
> release whether or not the steps in the CG were followed.

Well, I introduced new CG additions to that effect a few weeks ago:
https://sourceforge.net/p/testlilyissues/issues/5837/
So, it’s still fairly recent.

V.

https://codereview.appspot.com/551650043/



Web: update documentation symlinks, and use https in RewriteRules (issue 551650043 by v.villen...@gmail.com)

2020-04-09 Thread v . villenave
Reviewers: ,

Message:
This seems trivial enough; may I just push onto staging?

Cheers,
V.

Description:
Web: update documentation symlinks, and use https in RewriteRules

Please review this at https://codereview.appspot.com/551650043/

Affected files (+4, -4 lines):
  M Documentation/web/server/lilypond.org.htaccess


Index: Documentation/web/server/lilypond.org.htaccess
diff --git a/Documentation/web/server/lilypond.org.htaccess 
b/Documentation/web/server/lilypond.org.htaccess
index 
480fc3d5a795d21afdeb09e9b4d80860245941f4..5b83bfe5213f3e822e7083802fe9890c08adf36c
 100644
--- a/Documentation/web/server/lilypond.org.htaccess
+++ b/Documentation/web/server/lilypond.org.htaccess
@@ -18,7 +18,7 @@ RewriteEngine On
 
 # Permanent redirect from www.lilypond.org to lilypond.org
 RewriteCond "%{HTTP_HOST}" "^www\.(.+)$" [NC]
-RewriteRule "^/?(.*)$" "http://%1/$1"; [R=301,L,NE]
+RewriteRule "^/?(.*)$" "https://%1/$1"; [R=301,L,NE]
 
 # Deny following of symlinks by robots.
 # HTTrack is a known offender.
@@ -52,8 +52,8 @@ RedirectMatch ^/doc/stable/?$ /manuals
 RedirectMatch ^/doc/development/?$ /development
 
 # Allow to use deep links to latest stable or development docs
-RedirectMatch ^/doc//*latest/*(.*)$ /doc/v2.19/$1
-RedirectMatch ^/doc//*development/*(.*)$ /doc/v2.19/$1
+RedirectMatch ^/doc//*latest/*(.*)$ /doc/v2.21/$1
+RedirectMatch ^/doc//*development/*(.*)$ /doc/v2.21/$1
 RedirectMatch ^/doc//*stable/*(.*)$ /doc/v2.20/$1
 RedirectMatch ^/doc//*([^v].*)$ /doc/v2.20/$1
 RedirectMatch ^(/Documentation.*)$ /doc/v2.20$1
@@ -96,7 +96,7 @@ RewriteCond %{REQUEST_URI} !^/website
 # ...and does not start with /doc$
 RewriteCond %{REQUEST_URI} !^/doc$
 # ...add trailing slash for [menu] and to avoid /web/ in browser url
-RewriteRule ^(.+)$ http://%{HTTP_HOST}/$1/ [R,QSA,L]
+RewriteRule ^(.+)$ https://%{HTTP_HOST}/$1/ [R,QSA,L]
 
 # Request that does not start with /website
 RewriteCond %{REQUEST_URI} !^/website