Hi there,

We have 2 contexts
A web app context handling /
A ContextHandler with ResourceHandler with etags turned on handling /html

When we try to access something from the /html directory, the first time it 
works.  ( it only goes to the ContextHandler )
When we try to access it a second time the Resource handler returns a 304 and 
does not set Committed to true ( approx. line 283 of Resource handler ) and so 
it falls back to the web app context.   Our WebAppContext doesn't know how to 
handle it, and so errors.
When we try a 3rd time, it's back to working.


This used to work for us on Jetty 9.3.9.v20160517  but when we upgraded to 
jetty 9.4.6.v20170531 it broke,  I'm not sure if this expected behavior or not.

For now we've made our webapp context ignore paths starting with /html, but 
this seems like the wrong approach.  Shouldn't the resource handler be setting 
handled to true ?

Cheers,

David Beleznay


_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to