Here another CORS headache, but with a slightly different setup #919
Unanswered
SmartPhoneLover
asked this question in
Q&A
Replies: 2 comments
-
This is the output of curl for "https://files..com":
|
Beta Was this translation helpful? Give feedback.
0 replies
-
This is the output of the other error:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
shlink-web-client version
3.10.2
How do you use shlink-web-client
Docker image
Summary
After posting the same question in the wrong repo, I create it here again, but explaining the situation a bit better.
THE ISSUE
After trying to add the Shlink instance (by now only a single one) into Shlink Web Client, I see the following error in the web console of my browser:
[HTTP/3 404 Not Found 343ms]
Cross-Origin Request Blocked: Same-Origin Policy disallows reading the remote resources at https://<subdomain>.<base_domain>.xxx/rest/v3/health. (Reason: Unsuccessful CORS request). Status code: (null)
So, it's a bit different thatn others I have seen there, as the error message doesn't show anything related to missing headers, or cookies. It's actually the same error as shown here, with a different setup.
I have tried enabling/disabling some settings from my CF account (affected base domain), like: adding a page rule to disable security for the subdomain+base-domain affect; configuring the CORS section for the service in the CF tunnels (App Access) as: Access-Control-Allow-Origin (allow all origins), Access-Control-Allow-Methods (allow all methods), Access-Control-Allow-Headers (allow all http headers) and Access-Control-Max-Age (86400) + a Login policy to allow everyone to access to it. But, nothing worked.
I also tried with the public (official) Shlink Web Client version, but the same error:
[HTTP/3 404 Not Found 343ms]
Cross-Origin Request Blocked: Same-Origin Policy disallows reading the remote resources at https://<subdomain>.<base_domain>.xxx/rest/v3/health. (Reason: Unsuccessful CORS request). Status code: (null)
MY SETUP
My current setup consists of:
Environment...
Shlink stuff...
I have configured to use HTTPS (always), and the settings for the base domain for SSL as 'Full (strict)'.
Beta Was this translation helpful? Give feedback.
All reactions