Open KevinBoske opened 1 year ago
@KevinBoske I've had that issue as well with Metabolic Atlas, but it turned out Cloudfare was in fact blocking the request, since we could see it in the blocked requests panel. Are you sure that's not facing a similar situation?
Hi @KevinBoske, Sorry for the delay here, I was trying to find the error on our side but I'm not sure what it can be. This validation occurs on the backend and I'm able to acquire 200 response code with curl from the container running the server.
It may be as @mihai-sysbio says and there may be a block somewhere on the way to your website. Are you able to check? If this is not the case, I will have to debug the java code.
Just to clarify, "returns correctly for a browser" is exactly what happened with Metabolic Atlas. However, the webserver was trusting the local IP, and was thus serving the page. When the request came from Identifiers.org via some IP in Netherlands (or Belgium?), that IP was not trusted and the request was blocked. So, a publicly accessible link doesn't necessarily make it equally accessible to all clients.
I see a 403 with the home page (https://sagebionetworks.org/) returning a 403, even though it is publicly available and returns correctly for a browser.
I am unable to register.