I have problem with leaflet-geosearch OpenStreetMapProvider I get an error in console:
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3001' is therefore not allowed access.
That's a 503 error from the Nominatim server. 50x errors are failures on the web server side (not on your code), and a 503 is usually a temporary overload or outage. You'll have to wait it out.
Related
Getting repeatedly this error in Keycloak logs.
Attached below are the logs for reference:
The said client scope is not found if I try to search the same under Keycloak admin console too.
2022-09-22 04:04:12,718 ERROR [org.key.ser.err.KeycloakErrorHandler] (executor-thread-610) Uncaught server error: java.lang.IllegalStateException: Cached clientScope not found: 1e84ef04-9ef9-44fe-b1bd-f45e6d4 at org.keycloak.models.cache.infinispan.RealmAdapter.lambda$getClientScopesStream$3(RealmAdapter.java:1495) at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195) at java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1632) at
Steps to recreate:
Create client scope and attached to a client
Remove client scope attached with a client
Delete client scope
On the occurrence of this issue, I see well-known and many other endpoints to start giving 500 as they seem to be fetching cached scoped and doing certain validation
Any configuration miss that needs to be considered?
In my Ionic 4 Angular project I get the following error when requesting a json file from a server in my iOS simulator.
XMLHttpRequest cannot load https://myServer.com/api due to access control checks.
cordova.js:1540
Failed to load resource: Origin ionic://localhost is not allowed by Access-Control-Allow-Origin.
In the Chrome Browser with Access-Controls-origin plugin I do not get the error. How can I fix this issue?
You need to add ("Access-Control-Allow-Origin", '*') header at the requested resource.
Follow this link - 3 Ways to Fix the CORS Error — and How the Access-Control-Allow-Origin Header Works. The first option (install the moesif CORS extension) worked for me.
CORS errors are common in web apps when a cross-origin request is made but the server doesn't return the required headers in the response (is not CORS-enabled). It only happens when you're running the app from your localhost for testing purposes.
Checking the logs of a GCE Loadbalancer in the Google Cloud Platform Logs, shows a bunch of WARNINGs in the form of:
"GET https://<MY_DOMAIN>/.well-known/acme-challenge/*" 404 215 "Go-http-client/1.1"
and ..:
"GET https://<MY_SERVICE_DOMAIN>/*" 401 561 "Go-http-client/1.1"
What is causing these calls? Is it some kind of health check?
From what I gather from the docs, the readiness-probes of the backing Pods should be expected to be called. Also as far as I see the backend service groups are considered healthy.
As they appear as WARNINGs in the logs, I assume I should work on making them go away?
"GET https://<MY_DOMAIN>/.well-known/acme-challenge/*" 404 215 "Go-http-client/1.1"
That one is pretty straightforward and is caused by the Let's Encrypt protocol checking for your ownership over the domain. It's hard to say whether that's an actual error without knowing whether you were expecting Let's Encrypt to check that domain.
"GET https://<MY_SERVICE_DOMAIN>/*" 401 561 "Go-http-client/1.1"
Without knowing what MY_SERVICE_DOMAIN means, that's also hard to know, but I wouldn't expect readiness checks to involve the LoadBalancer since (as you correctly observed) that check should be at the Pod level, not from outside the cluster
As they appear as WARNINGs in the logs, I assume I should work on making them go away?
That likely is a personal preference. Without any question having those extraneous messages makes finding actual warnings harder, but I doubt they are actually hurting anything, either. The distinction to me would be whether some process is expecting a successful HTTP response to the MY_SERVICE_DOMAIN request, and when it doesn't receive one, that causes a downstream failure -- it won't be the LoadBalancer that would require action, but rather the consumer of it.
I'va noticed that if the requests send via REST consumer return an error (invalid scheme, connection refused, error 400, etc.) the REST consumer doesn't work anymore. To get it back, I had to reload the definition file.
I think that this may be a bug.
Moreover, during these tests, I've also noticed that not all the URL were accepted. For example, by omitting the "http://" Proton returns "invalid scheme" error. Whereas, URL with "-" isn't parsed correctly and the "connection refused" error is returned.
It'd very helpful to have a list of prohibited characters.
Thanks.
Existent file. http://us.battle.net/d3/static/images/layout/site-bg/body-bg-1680px.jpg
Nonexistent file. http://us.battle.net/d3/static/images/layout/site-bg/body-bg-2500px.jpg
Normally, web server should give an error like: "Not found. The requested document was not found on this server."
However, trying to reach a missing image loads Battle.net's own 404 page.
How do they handle it? .htaccess? front controllers? custom webserver configuration?
It depends on the webserver being used. In apache there are configuration options to set custom paths for error responses including 404, e.g.
ErrorDocument 404 /somewhere/customMessage.html
ErrorDocument 500 /somewhere/differentMessage.html
So that would go in the apache config or you could put it in .htaccess.