-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https url changed to http and connection with https #22
Comments
From a quick look at the code, it seems the URL is being selected here: So my guess is that the http version is being returned via an API request as documented at https://docs.openmicroscopy.org/omero/5.6.0/developers/json-api.html#list-starting-urls I don't know if there's any reason why those aren't https. I feel like QuPath ought to be getting the server URL to use from the API... so if https://dkfz-omero-test.de/api/v0/ doesn't return something usable, I'm not sure what should be done about that on the QuPath side. (PS. The person who did most of the recent work on the OMERO extension left some months ago, and it is likely to take a bit of time before it's actively maintained again. I started some major refactoring because of #21 but I'm not really on top of the code yet - and it may take a while before I can get back to it.) |
Linking to the original discussion: https://forum.image.sc/t/qupath-omero-login-problem/71577 |
Hi @petebankhead, Thank you for your reply. You are correct all the urls returned by: |
Any updates on this? I am encountering the same issue. Thanks. |
@MicheleBortol @mkreisel we came across this issue recently ourselves. You are correct that the underlying issue with the current qupath-extension-omero is that the URLs reported by the OMERO.web api endpoint should be Solving this is rather an OMERO.web/nginx configuration issue than a QuPath issue. If nothing else works, you should be able to set the internal property Independently of the Web/nginx configuration, it also feels like qupath-extension-omero could more gracefully handle the 301 response especially if the case like this one where the protocol is redirected from http to https. |
@mkreisel @sbesson Setting the omero web config property: |
Dear all,
When I tryto connect to our OMERO server through the extension with:
Extensions > OMERO > Browse server > New server
and then pasting the URL I use for OMERO web:https://dkfz-omero-test.de
I get the following error:So it seems that the url is converted from
https
tohttp
before the request is made to the server.This requested is redirected by our nginx setup to the same url in
https
with a 301 redirection. Could you confirm if I am interpreting this correctly?Interestingly, when I change the redirection code in our nginx config from a 301 to a 302 it seems that the response is accepted, but then I immediately get the following error.
I am on windows 10 with QuPath 0.32 and the Omero Extension 0.3 connecting to OMERO.web 5.11.0 (OMERO.server 5.6.3-ice36-b228).
Is there a way to use the extension to connect to OMERO using https? Or another way around these errors?
Thank you.
Best,
Michele
The text was updated successfully, but these errors were encountered: