Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSS and images not working with ESAPIWebApplicationFirewallFilter #296

Closed
meg23 opened this issue Nov 13, 2014 · 4 comments
Closed

CSS and images not working with ESAPIWebApplicationFirewallFilter #296

meg23 opened this issue Nov 13, 2014 · 4 comments

Comments

@meg23
Copy link

meg23 commented Nov 13, 2014

From shrey.aw...@gmail.com on December 03, 2012 13:07:04

What steps will reproduce the problem? I have integrated ESAPIWebApplicationFirewallFilter in my existing application. Application has started up fine and there is no error in logs but I am not able to see any frames and images on the page only text box is visible, still able to log in to application but again only text is visible after log in. The application is developed using Spring MVC,
if I change the filter to ESAPIFilter it works fine. What is the expected output? What do you see instead? Expected web page with images and headers, only could see text boxes. What version of the product are you using? On what operating system? 2.0 Does this issue affect only a specified browser or set of browsers? All browsers. Please provide any additional information below.

Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=290

@xeno6696
Copy link
Collaborator

@kwwall There simply isn't enough information here to be able to recreate this issue in the slightest. Typically I would need

1.) Copy of the affected .css file, or snippets OR
2.) Copy of a small web app demonstrating the problem.

This sounds to me like they need to customize the AntiSamy file, but there just isn't enough information here to be able to take any action.

@kwwall
Copy link
Contributor

kwwall commented Jul 28, 2017

@xeno6696 "Closed because there is not sufficient information presented to reproduce the problem" is always a valid reason for closing an issue in my book. It's just too bad that it took us 5 years or so to get to that point.

Perhaps we should add a "Cannot reproduce" label. I thought of using "wontfix" label, but it's not really like we won't fix it, but rather can't because we are lacking sufficient information to reproduce it.

@xeno6696
Copy link
Collaborator

For tags, I like "insufficient-info"

@kwwall
Copy link
Contributor

kwwall commented Jul 29, 2017

Works for me. I'll add it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants