calibre

Bug #2004197
Comment #6

Comment 6 for bug 2004197

Revision history for this message

obix (e-chomas-g) wrote on 2023-01-31:

No proxy and no special caching policy (as far as I know).

Retried with a fresh setup of calibre on my local machine (server localhost) with 3 different browsers - same behaviour.

I now used wirshark to look at the communication with my server. After pressing reload button in viewer there is a GET-Request to the server with a query parameter different from the "original" viewer query and one gets e.g. the following response (in this example containing the just updated content "15"):

Transmission Control Protocol, Src Port: 8080, Dst Port: 37654, Seq: 1, Ack: 711, Len: 465
Hypertext Transfer Protocol
    HTTP/1.1 200 OK\r\n
    Accept-Ranges: bytes\r\n
    Content-Length: 227\r\n
    Content-Type: text/html; charset=UTF-8\r\n
    Date: Tue, 31 Jan 2023 16:10:56 GMT\r\n
    ETag: "f8efb6c2c4432fecec64a22d311834d760a18a41"\r\n
    Keep-Alive: timeout=120\r\n
    Server: calibre 6.11.0\r\n
    \r\n
    [HTTP response 1/2]
    [Time since request: 0.016127509 seconds]
    [Request in frame: 37]
    [Next response in frame: 2701]
    [Request URI: http://calibre:8080/book-file/1127/TXT/2/16751778230/index.html?library_id=Calibre-Bibliothek&1675181456173]
    File Data: 227 bytes
Line-based text data: text/html (1 lines)
    {"version":1,"tree":{"n":"html","c":[{"n":"head","x":"\n ","l":"\n ","c":[{"n":"title","x":"Unbekannt","l":"\n \n "}]},{"n":"body","x":"\n","c":[{"n":"p","x":"15","l":"\n"}]}]},"ns_map":["http://www.w3.org/1999/xhtml"]}

But the update content ("15") is displayed in the viewer not before a hard reload.

Having no idea of ajax but just wondering, if there might be a problem with the viewer component not recognizing to show updated data (version numbering)?

Sorry for the blind guess but I have no idea what could cause unwanted caching on the client/browser side, especially when using 3 different browsers talking to localhost or the local server.

Still hoping you (or someone else) might have an idea what's causing this behaviour.

Thanks for your support and this great software!

No proxy and no special caching policy (as far as I know).

Retried with a fresh setup of calibre on my local machine (server localhost) with 3 different browsers - same behaviour.

Transmission Control Protocol, Src Port: 8080, Dst Port: 37654, Seq: 1, Ack: 711, Len: 465
Hypertext Transfer Protocol
    HTTP/1.1 200 OK\r\n
    Accept-Ranges: bytes\r\n
    Content-Length: 227\r\n
    Content-Type: text/html; charset=UTF-8\r\n
    Date: Tue, 31 Jan 2023 16:10:56 GMT\r\n
    ETag: "f8efb6c2c4432fecec64a22d311834d760a18a41"\r\n
    Keep-Alive: timeout=120\r\n
    Server: calibre 6.11.0\r\n
    \r\n
    [HTTP response 1/2]
    [Time since request: 0.016127509 seconds]
    [Request in frame: 37]
    [Next response in frame: 2701]
    [Request URI: http://calibre:8080/book-file/1127/TXT/2/16751778230/index.html?library_id=Calibre-Bibliothek&1675181456173]
    File Data: 227 bytes
Line-based text data: text/html (1 lines)
    {"version":1,"tree":{"n":"html","c":[{"n":"head","x":"\n    ","l":"\n  ","c":[{"n":"title","x":"Unbekannt","l":"\n    \n  "}]},{"n":"body","x":"\n","c":[{"n":"p","x":"15","l":"\n"}]}]},"ns_map":["http://www.w3.org/1999/xhtml"]}

But the update content ("15") is displayed in the viewer not before a hard reload.

Having no idea of ajax but just wondering, if there might be a problem with the viewer component not recognizing to show updated data (version numbering)?

Sorry for the blind guess but I have no idea what could cause unwanted caching on the client/browser side, especially when using 3 different browsers talking to localhost or the local server.

Still hoping you (or someone else) might have an idea what's causing this behaviour.

Thanks for your support and this great software!