On Oct 30, 2007, at 10:11 AM, Chris Chen wrote:

> Scott,
> Here's the document and the workaround that Confluence has been using
> for quite some time:
> http://confluence.atlassian.com/display/DOC/Known+Issues+for+Resin+3.x
> Some of the configuration issues were likely due to the strictness of
> Resin's validation.  The interesting one that I'm referring to is the
> workaround for filter mappings as described in the doc where the
> following
> <dispatcher>REQUEST</dispatcher>
> <dispatcher>FORWARD</dispatcher>
> needed to be added to get things to work under Resin 3 whereas Tomcat
> or others didn't seem to have this issue. I'm wondering what the
> reason for this is and whether the servlet spec was simply up for
> interpretation on that as was suggested by someone.

The spec is pretty clear on that case.  A missing <dispatcher> means  

There might be a case where Resin itself is calling forward() (e.g.  
for a login page?), when it should be treating the request as a top  
level request or calling sendRedirect.

>>> I'm wondering what Caucho's take on this is?  It seems like this is
>>> causing quite a lot of grief, and apparently there seems to be some
>>> problem with handling large image uploads as per the JIRA issue:
>>> http://jira.atlassian.com/browse/CONF-8637
>> I've filed this as http://bugs.caucho.com/view.php?id=2131.  I'm a
>> little confused by the discussion.  Does Coherence have a keepalive
>> option?  It shouldn't.
> Confluence doesn't, but I believe they are referring to the keepalive
> option in resin that may cause this issue.

Ok.  That makes more sense.

-- Scott

> -Chris
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest

resin-interest mailing list

Reply via email to