Using content server via a proxy

[Phssthpok]

I'm already running an SSL server and I've configured it to forward requests addressed to a specific domain name to my content server. I can now connect to my content server directly over the local net as http: //192.168.1.100:8080, or remotely as https: //www.foo.com. However, when I go via the proxy, it ignores all my sort/search criteria.

[NB: I'm deliberately putting a space after http: and https:, since otherwise they automatically get turned into links and the middle bit gets elided... there's probably a better way...]

If I use http: //192.168.1.100:8080/#book_id=3120&library_id=Library&panel=book_list&s earch=authors:%22%3DLewis%20Carroll%22&sort=author _sort.asc the result is as shown in the attached image (local.jpg).

If I use https: //www.foo.com/#book_id=3120&library_id=Library&panel=book_list&s earch=authors:%22%3DLewis%20Carroll%22&sort=author _sort.asc the result is as shown in the attached image (remote.jpg).

All the proxy does is to forward all requests addressed to https: //www.foo.com/ to http: //127.0.0.1:8080, and forward the responses from the content server back to the user. I presume there's some clever Javascript that isn't making the leap from the SSL server to the Calibre content server...

Any ideas what the problem is here, and what I can do about it?

[kovidgoyal]

Look at the server logs, the proxy logs and the console in the browser. One of those locations will tell you which requests your proxy server is not forwarding/mangling.