Your comments
No worries thanks for laying it out, good reasoning.
Thanks for the info Tom, I'll keep digging on my side as well. I'll let you know if I can find anything in regards to how a 302 is being handled and if I need a configuration change on the conf file.
Oh I've patched and rebooted since then. When I inspect the element via dev tools I do see that its trying to go to <a href="/comics/" id="comics">Comics</a>. (Or https://mysite.com/comics).
But when clicking on the link its redirected without a HTTPS to http://mysite.com/comics/1/ after I click on it. Might not like the fact that my comics root is comics, but that is just a guess...
Thanks for trying to help :)
So I added the "SSLProxyEngine on" with no impact either good or negative. Then I tried with proxy settings for a prefix and that broke things.
I then unchecked the box for single root folder, which is comics for me. So I login and I see Comics with the balloon icon. Then I click comics (my single root folder) again and now the https is staying persistent for me. So interesting so in my file structure I have a single root folder called comics then I have DC, Marvel etc under that, for some reason when the option for "Bypass single root folder" is enabled it breaks https: from staying persistent when comics is clicked on and redirected to http:
Hope I explained that well! :)
I'm using an apache proxy with these settings below, edits for privacy sake. As for 1.0 I wasn't running a proxy, this is a new setup at the moment. I could try the 1.0 though.
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerAdmin Email@somewhere.com
ServerName comicsdb.places.com
DocumentRoot /var/www/html
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on
# A self-signed (snakeoil) certificate can be created by installing
# the ssl-cert package. See
# /usr/share/doc/apache2/README.Debian.gz for more info.
# If both key and certificate are stored in the same file, only the
# SSLCertificateFile directive is needed.
SSLCertificateFile /etc/letsencrypt/live/places.com/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/places.com/privkey.pem
# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# concatenation of PEM encoded CA certificates which form the
# certificate chain for the server certificate. Alternatively
# the referenced file can be the same as SSLCertificateFile
# when the CA certificates are directly appended to the server
# certificate for convinience.
SSLCertificateChainFile /etc/letsencrypt/live/bastmail.net/chain.pem
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<Directory /usr/lib/cgi-bin>
SSLOptions +StdEnvVars
</Directory>
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:2202/
ProxyPassReverse / http://127.0.0.1:2202/
</VirtualHost>
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
Other than the redirect to http on selecting my root folder everything works as expected.
Thanks Matthieu
The issue you are having is that OPDS honors the data xml file within the CBR/CBZ before the file name. I've found that if you open the file (CBR) with winrar and delete the offending xml and rescan the library. Pain in the butt for sure, but it works.
Tom if you get a chance that would be a nice option for us to choose if its easy to code. Thanks as alway man!
Customer support service by UserEcho
Thanks Tom, I just came here to check for this. Keep up the great work!