You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2006/01/30 16:28:49 UTC
DO NOT REPLY [Bug 37867] - Filter mapping to wide
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37867>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37867
------- Additional Comments From rwallace@thewallacepack.net 2006-01-30 16:28 -------
I am also running into this problem. Any images and css files that the browser
tries to load are being rejected by the filters. For example:
2006-01-27 10:31:20,241 54531 DEBUG [http-8080-Processor24]
org.apache.shale.application.AbstractRegExpFilter
(AbstractRegExpFilter.java:171) - execute(/styles/mpl.css)
2006-01-27 10:31:20,242 54532 DEBUG [http-8080-Processor24]
org.apache.shale.application.AbstractRegExpFilter
(AbstractRegExpFilter.java:203) - reject(not include)
2006-01-27 10:31:20,292 54582 DEBUG [http-8080-Processor24]
org.apache.shale.application.AbstractRegExpFilter
(AbstractRegExpFilter.java:171) - execute(/images/mpl_logo_large.gif)
2006-01-27 10:31:20,293 54583 DEBUG [http-8080-Processor24]
org.apache.shale.application.AbstractRegExpFilter
(AbstractRegExpFilter.java:203) - reject(not include)
That is with the following chain configuration:
<command className="org.apache.shale.application.ContextRelativePathFilter"
includes="\S*\.xml,\S*\.faces,\S*\.html,\S*\.gif,\S*\.jpg,/index\.jsp"
excludes="\S*\.jsp,\S*\.jspf"/>
I also tried to add a \S*.css to allow css files, with no luck. Next, I tried
commenting out the command completely to totally disable filtering, but that
didn't work either.
I think the reason it doesn't show up in the use-cases is that all the images
used there are on external URLs, like the struts logo. All the css is inlined
within the pages. So there really are no resources that are being loaded by the
browser from the webapp itself.
What is really confusing is that it still happens even if I remove the filter
from the chain configuration, as if Shale is inserting a default filtering chain
rule. So, maybe the bug is that Shale is inserting it regardless if one exists
or not, so the configuration is being overridden by whatever Shale inserts by
default. I haven't looked at the code yet, but that's what it looks like from
observation.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org