Could you support an SSL=true configuration option in config.inc.php? My host is not SSL, which means that some links (such as straight after login) are 404 broken.
Could you support an SSL=true configuration option in config.inc.php? My host is not SSL, which means that some links (such as straight after login) are 404 broken.
<!-- github-sync-id:299499894 -->
I don't understand your request. Piwigo works fine on both HTTP or HTTPS on the same installation without any specific configuration. See http://demo.piwigo.com and https://demo.piwigo.com (even if we will certainly automatically redirect HTTP to HTTPS soon)
I don't understand your request. Piwigo works fine on both HTTP or HTTPS on the same installation without any specific configuration. See http://demo.piwigo.com and https://demo.piwigo.com (even if we will certainly automatically redirect HTTP to HTTPS soon)
<!-- github-comment-id:367939550 -->
I have an https front end reverse proxy (nginx) proxying to a backend apache server using http. When I login I get a 404 error (the protocol changes from https:// to http:// in my browser)
I have an https front end reverse proxy (nginx) proxying to a backend apache server using http. When I login I get a 404 error (the protocol changes from https:// to http:// in my browser)
<!-- github-comment-id:368156224 -->
Just to add some information: I could setup a redirect from http to https (but that would be insecure), but my request is that either piwigo stay on the same protocol throughout, or that there be an option to force piwigo to use SSL all the time.
Just to add some information: I could setup a redirect from http to https (but that would be insecure), but my request is that either piwigo stay on the same protocol throughout, or that there be an option to force piwigo to use SSL all the time.
<!-- github-comment-id:368161298 -->
Proxying NGINX to Apache+mod_php is a rather awkward setup (why not use some PHP fastcgi interpreter like php-fpm or uwsgi behind nginx?). Instead of requesting a workaround for such a setup in Piwigo which would be barely useful for anyone, you could enable SSL on apache, either using a self-signed cert or one from letsencrypt. Easy fix.
You could also try setting RequestHeader set X-Forwarded-Proto "https" in Apache for the Piwigo vhost/location, not sure if PHP will eat this though (check $_SERVER['HTTPS'] in phpinfo()).
In any case, it's a server setup issue rather than a Piwigo issue.
Proxying NGINX to Apache+mod_php is a rather awkward setup (why not use some PHP fastcgi interpreter like php-fpm or uwsgi behind nginx?). Instead of requesting a workaround for such a setup in Piwigo which would be barely useful for anyone, you could enable SSL on apache, either using a self-signed cert or one from letsencrypt. Easy fix.
You could also try setting `RequestHeader set X-Forwarded-Proto "https"` in Apache for the Piwigo vhost/location, not sure if PHP will eat this though (check $_SERVER['HTTPS'] in phpinfo()).
In any case, it's a server setup issue rather than a Piwigo issue.
<!-- github-comment-id:374047318 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Could you support an SSL=true configuration option in config.inc.php? My host is not SSL, which means that some links (such as straight after login) are 404 broken.
I don't understand your request. Piwigo works fine on both HTTP or HTTPS on the same installation without any specific configuration. See http://demo.piwigo.com and https://demo.piwigo.com (even if we will certainly automatically redirect HTTP to HTTPS soon)
I have an https front end reverse proxy (nginx) proxying to a backend apache server using http. When I login I get a 404 error (the protocol changes from https:// to http:// in my browser)
Just to add some information: I could setup a redirect from http to https (but that would be insecure), but my request is that either piwigo stay on the same protocol throughout, or that there be an option to force piwigo to use SSL all the time.
Proxying NGINX to Apache+mod_php is a rather awkward setup (why not use some PHP fastcgi interpreter like php-fpm or uwsgi behind nginx?). Instead of requesting a workaround for such a setup in Piwigo which would be barely useful for anyone, you could enable SSL on apache, either using a self-signed cert or one from letsencrypt. Easy fix.
You could also try setting
RequestHeader set X-Forwarded-Proto "https"in Apache for the Piwigo vhost/location, not sure if PHP will eat this though (check $_SERVER['HTTPS'] in phpinfo()).In any case, it's a server setup issue rather than a Piwigo issue.