Hi Mark
Am Freitag, 8. Februar 2019, 09:30:32 CET schrieb Jörg Schaible:
> Hi Mark,
>
> Am Mittwoch, 6. Februar 2019, 15:32:26 CET schrieb Mark Thomas:
>
> [snip]
>
> > You need to set cors.allowed.origin to an appropriate value. See:
> > http://tomcat.apache.org/tomcat-9.0-doc/config/filter.ht
Hi Mark,
Am Mittwoch, 6. Februar 2019, 15:32:26 CET schrieb Mark Thomas:
[snip]
> You need to set cors.allowed.origin to an appropriate value. See:
> http://tomcat.apache.org/tomcat-9.0-doc/config/filter.html#CORS_Filter
thanks for your pointers, but unfortunately even setting the value to '*'
On 06/02/2019 12:48, Jörg Schaible wrote:
> Hi Mark,
>
> Am Mittwoch, 6. Februar 2019, 11:45:46 CET schrieb Mark Thomas:
>> Exact Tomcat 8 version?
>> Exact Tomcat 9 version?
>>
>> How is CORS configured in your application?
>
> the VersionLoggerListener entries from the catalina.log files:
>
>
Hi Mark,
Am Mittwoch, 6. Februar 2019, 11:45:46 CET schrieb Mark Thomas:
> Exact Tomcat 8 version?
> Exact Tomcat 9 version?
>
> How is CORS configured in your application?
the VersionLoggerListener entries from the catalina.log files:
this is the machine with Tomcat 8:
== %< ==
Exact Tomcat 8 version?
Exact Tomcat 9 version?
How is CORS configured in your application?
Mark
On 06/02/2019 10:36, Jörg Schaible wrote:
> Hi,
>
> we have a strange symptom after an upgrade from Tomcat 8 to Tomcat 9, because
> we get a 403 for a call that works flawlessly with the previous
Hi,
we have a strange symptom after an upgrade from Tomcat 8 to Tomcat 9, because
we get a 403 for a call that works flawlessly with the previous version.
Let's describe the scenario: We have a customer with a Wordpress application
hosted on an Apache server. Some pages perform XMLHttpRequests