Default servlet cannot serve large filtered content

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 6.1.18
  • Fix Version/s: 6.1.19
  • Component/s: Servlet
  • Labels:
    None

Description


If static content is too large to fit in the content cache, the request is filtered, but the response is not, then default servlet is unable to serve the content.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ory Warshenbrot added a comment -

This especially seems to happen in web applications that use SiteMesh's PageFilter or Acegi Security where the static content is larger than the "maxCacheSize" attribute of DefaultServlet.

Show
Ory Warshenbrot added a comment - This especially seems to happen in web applications that use SiteMesh's PageFilter or Acegi Security where the static content is larger than the "maxCacheSize" attribute of DefaultServlet.
Hide
Permalink
Greg Wilkins added a comment -

Indeed - sitemesh plus status content too large to fit into the cache would trigger this bug.
But it is fixed in 6.1.19
cheers

Show
Greg Wilkins added a comment - Indeed - sitemesh plus status content too large to fit into the cache would trigger this bug. But it is fixed in 6.1.19 cheers

People

  • Assignee:
    Unassigned
    Reporter:
    Greg Wilkins
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: