-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Header image for Jetty demo page fails on hard refresh #9078
Comments
Sounds like a problem with an If-Not-Modified response. My guess is we are sending a 304 not modified, but also setting content-length. @lorban do you want to take this? |
Signed-off-by: Ludovic Orban <[email protected]>
@gregw I managed to reproduce the problem. See #9079 for a reproducing test and a prototype fix which should be discussed with @lachlan-roberts. But at least it solves the problem for now so maybe we want to merge it right away and clean it later? It's not surprising we did not catch this earlier because we need to serve a file of a certain size otherwise it's not mmap'ed and the slow path is taken. |
Signed-off-by: Ludovic Orban <[email protected]>
Signed-off-by: Ludovic Orban <[email protected]>
Signed-off-by: Ludovic Orban <[email protected]>
…teBuffer instances and document that contract Signed-off-by: Ludovic Orban <[email protected]>
…teBuffer instances and document that contract Signed-off-by: Ludovic Orban <[email protected]>
…x-document-modules * upstream/jetty-12.0.x: Issue jetty#9167 - making assumption in flaky test jetty 12.0.x cleanup duplicate osgi pom metadata (jetty#9093) Jetty 12 - Add tests in util/resource for alternate FileSystem implementations (jetty#9149) Cleanup non-retainable `Retainable`s (jetty#9159) Fixes retainability of special Chunks (jetty#9073) TCK: Dispatch forward and includes attributes do not meet the spec (jetty#9074) re-enable h3 tests (jetty#8773) More fundamental test case Reorganization of jetty-client classes. (jetty#9127) Removing @disabled from SslUploadTest Removing @disabled from jetty-start jetty#9134 added test ee10: DefaultServlet: Replace checks for isStreaming() by !isWriting() jetty#9078 make HttpContent.getByteBuffer() implementations return new ByteBuffer instances and document that contract Fixes jetty#9141 - Thread-safe Content.Chunk#slice (jetty#9142) Remove `@Disabled` from `jetty-jmx` (jetty#9143) Bump maven.version from 3.8.6 to 3.8.7 Bump maven.version from 3.8.6 to 3.8.7
Jetty version(s)
Jetty 12
Java version/vendor
openjdk version "19.0.1" 2022-10-18
OS type/version
macOS Monterey 12.6.2
Description
When running the
demos
module that ships with Jetty 12, I am seeing some odd behavior upon accessing the demo home page at http://0.0.0.0:8080/.When the page first loads, everything looks fine. But if I do a hard refresh (Cmd+Shift+R), the header image no longer appears and I get the following stacktrace in my terminal:
The fact that the page loads correctly at first and only breaks upon refresh is what seems particularly weird to me here.
How to reproduce?
$ java -jar $JETTY_HOME/start.jar --add-modules=demos $ java -jar $JETTY_HOME/start.jar
Then navigate to http://0.0.0.0:8080/. The page loads correctly upon first load, but if I do a hard refresh (Cmd+Shift+R) the image no longer appears.
The text was updated successfully, but these errors were encountered: