Quote:
Originally Posted by chaley
Well, it doesn't work for me. I run calibre behind apache in reverse proxy mode, which means that calibre doesn't see anything if the url doesn't have the prefix. The IP address gets the main page for the virtual host. Supporting reverse proxy is why the url-prefix was added.
Why are you using a url-prefix when calibre is listening directly to the IP address?
In any event, supporting the use case of calibre directly listening to an IP but having a url-prefix isn't worth it for me. I suspect that you might be the only CC user who would use it.
|
Calibre is always listening directly on an IP, otherwise there's nothing to proxy - the reverse proxy is typically for use from outside the network, which is why I have a url-prefix... for the reverse proxy connection. When I talk about using curl in my post above, I'm hitting the internal IP of calibre-server directly, avoiding the (in my case) nginx server acting as the proxy. I'm talking about autodiscovery, which implies using it inside my own network. Calibre-companion even takes that distinction into account with the ability to have separate configuration for "external" and "internal" connections. Auto discovery only typically works internally anyway.
I'm making a suggestion for a feature improvement that currently has a potentially very confusing failure mode to people who are technical enough to follow directions on a message board, but not technical enough to adequately troubleshoot problems (apparent success, including authentication, then simply having no book list), which I would assume actually encompasses a large number of CC users. It became annoying as a user when I made the same custom configs on 5 different devices, and I wondered if I could automate it - probably a side effect of my day job as an tooling and automation developer. Once something has been done two or three times, it's time to find or write a tool to stop having to do it yourself.
At the very least, CC should probably pop up an error dialog if the "/opds" link is not available, which would gently nudge users in the correct direction. It would also give an easily searchable consistent message in the form of the error text.
This would be more properly placed as an improvement or enhancement request in a bug tracker. I don't see that CC has one of those, so I put it here.