-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 2/6/15 11:58 AM, Mark Eggers wrote:
CORS basically doesn't with Internet Explorer 10.
IE 8, and CORS does not work at all. IE 8 - Microsoft has a
'special mechanism' for CORS IE 9 - Microsoft breaks the 'special
mechanism' IE 10 -
On 05/02/2015 23:14, Brian wrote:
Hello David,
Not, it is not the case. No exceptions whatsoever. And about 1/100 (or less)
of the requests return a 403 to the users, and all those requests are doing
the same thing.
Thanks a lot for your help!
Is any authentication configured for this
On 06/02/2015 10:21, Brian wrote:
Hello Mark,
1- No authentication at all, since the user authenticates sending a parameter
in the query string.
2- I have two filters: org.tuckey.web.filters.urlrewrite.UrlRewriteFilter
(which has been working fine for years now) and CORS, yes!!!
Hello Mark,
1- No authentication at all, since the user authenticates sending a parameter
in the query string.
2- I have two filters: org.tuckey.web.filters.urlrewrite.UrlRewriteFilter
(which has been working fine for years now) and CORS, yes!!!
Actually, the CORS filter
http://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#CORS_Filter
The filter works by adding required Access-Control-* headers to
HttpServletResponse object. The filter also protects against HTTP response
splitting. If request is invalid, or is not permitted, then request is
rejected with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/6/2015 2:21 AM, Brian wrote:
Hello Mark,
1- No authentication at all, since the user authenticates sending a
parameter in the query string.
2- I have two filters:
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter (which has
been
On 6 February 2015 at 02:42, Brian brian...@emailbb.com wrote:
Hi,
I have a Restful service that receives a huge amount of HTTP requests per
day. In some of these requests, Tomcat returns an HTTP 403 error status.
Your servlet does something which throws a java.lang.Security exception
Hello David,
Not, it is not the case. No exceptions whatsoever. And about 1/100 (or less) of
the requests return a 403 to the users, and all those requests are doing the
same thing.
Thanks a lot for your help!
-Original Message-
From: David Bullock
