Category: | Bug report |
Priority: | Normal |
Status: | New |
Project: | Severity: | Major |
Resolution: | Open |
|
Component: | Reproducibility: | Always |
Assigned to: |
If you set your CORS filter to */*, jasperserver UI will be giving you 403 error whenever you try navigate home after generating a report.
The logs will remain clean.
Steps to reproduce the bug.
1) Configure web.xml file to use CORS filter
2) Restart jasperserver
3) Generate a report
4) Press "home" button
You will receive error 403.
Configure jasperserver\WEB-INF\Web.xml file.
<filter>
<filter-name>CorsFilter2</filter-name>
<filter-class>org.apache.catalina.filters.CorsFilter</filter-class>
<init-param>
<param-name>cors.allowed.origins</param-name>
<param-value>*</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>CorsFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
v6.1.1
2 Comments:
Hi,
I am facing the same issue .Any luck on this ?
Hello,
We've encounter a strange behaviour with version 6.3.0 and all browsers except IE. We were able to connect to the Jasper login page but few seconds after the page display we received the message "connection error try reloading".
There were no clue in tomcat or Jasper logs and after hours of search on internet i found your post and remembered that we added CORS filters in the web.xml for another webapp. We disabled the CORS filters and we recovered total access with any browser to our Jasper server.
So thank you for your post it gave me the way to solve my problem. Hope you've find how you solved your problem.
Best regards
Horseman