>
>
> > Tomcat uses the same code for static and class loader resources but it
> > is meant to distinguish between the two. However, it looks like there is
> > a bug in Tomcat's resource handling that hides this resource once the
> > static look-up fails. I need to dig into this some more.
>
> Yes,
On 18/05/18 07:23, Mark Thomas wrote:
> Tomcat uses the same code for static and class loader resources but it
> is meant to distinguish between the two. However, it looks like there is
> a bug in Tomcat's resource handling that hides this resource once the
> static look-up fails. I need to dig
On 17/05/2018 15:43, Jeremy Collins wrote:
At this point we're unsure if this is an actual bug in Tomcat or an
incorrect usage of getResourceAsStream(path) on our part so
we're looking for advice.
I think it is a bit of both.
ServletContext.getResourceAsStream(path) won't normally return a
Hi,
We're seeing an issue with how WebResources are cached that started
occurring in Tomcat 8.0.39 (we're using Ubuntu Xenial but I don't believe
it's related to anything in the OS).
Some of the CSS/JS files that we serve are packed inside JAR files. These
files are served by a filter that list
