Hi Greg,
Thank you for your reply.
My embed code actually defines a web.xml descriptor with the
following relevant snippet:
<!-- Default Jetty Servlet for static content and
directory listings !-->
<servlet>
<servlet-name>default</servlet-name>
<servlet-class>org.eclipse.jetty.servlet.DefaultServlet</servlet-class>
<init-param>
<param-name>dirAllowed</param-name>
<param-value>true</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>default</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
Following your lead of checking the descriptor I found this:
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/servlet/DefaultServlet.html
Which references settings like:
maxCacheSize : 0 for no cache
cacheControl : If set, all static content will have
this value set as the cache-control header.
I will try to either of those and hopefully that's all I need.
Thanks,
On 3/9/2017 7:49 PM, Greg Wilkins
wrote:
Igal,
I don't think it is the jetty cache, as that only applies
to static content rather than JSPs.
It is probably the configuration of the JSP Servlet, which
would be in the webdefault.xml descriptor included in the
jetty-servlet.jar
The other thing to check is that it is not the browser
cache.
regards
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users