urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

test case potentially in progress

master
smcv 2018-01-08 06:05:36 -04:00 committed by admin
parent 8e280df9de
commit 92f365f798
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/bugs/cgi_redirecting_to_non-https_URL.mdwn
View File

@ -31,3 +31,15 @@ I think this might be to do with nginx not rewriting POST URLs when reverse-prox
they would be generated in an HTTP form in any case, except perhaps by lighttpd's CGI handler since the back they would be generated in an HTTP form in any case, except perhaps by lighttpd's CGI handler since the back
end is HTTP. A workaround is for nginx to redirect any HTTP URI to the HTTPS equivalent. I initially disabled end is HTTP. A workaround is for nginx to redirect any HTTP URI to the HTTPS equivalent. I initially disabled
that so as to have the path for letsencrypt negotiation not redirected.-- [[Users/Jon]] that so as to have the path for letsencrypt negotiation not redirected.-- [[Users/Jon]]
> Do you have the `reverse_proxy` option set to 1? (It affects how ikiwiki generates
> self-referential URLs).
>
> Is the connection between nginx and lighttpd http or https?
>
> I think this is maybe a bug in `IkiWiki::redirect` when used in conjunction with
> `reverse_proxy: 1`. I'm in the process of adding a
>
> Assuming nginx has a reasonable level of configuration, you can redirect http to https
> for the entire server except `/.well-known/acme-challenge/` as a good way to bootstrap
> ACME negotiation. --[[smcv]]