Skip to content
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

Solr admin not acessible on HTTPS #34

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

introfini
Copy link

The Issue

If you follow the instructions to open the Solr Admin via HTTP (http://.ddev.site:8983/solr/) you are redirect automatically to HTTPS and that doesn't work.

How This PR Solves The Issue

Have the Solr Admin available also on HTTPS.

HTTPS_EXPOSE=8983:8983

Related Issue Link(s)

#33

@rfay
Copy link
Member

rfay commented Aug 7, 2023

I imagine you're using Firefox and it's redirecting. Unfortunately the Solr web UI doesn't really work right with https, which is why it's not added here.

@introfini
Copy link
Author

introfini commented Aug 7, 2023

Yes, I'm using Firefox. The web ui is working fine with me. But I haven't tested everything.

Thanks.

@rfay
Copy link
Member

rfay commented Aug 7, 2023

Yeah, try it with Chrome or other things that redirect. I don't know why it misbehaves, but this has been tried several times before. You can turn off that behavior in Firefox, please document how to do it here. Maybe a PR to the README explaining what's going on.

@tyler36
Copy link
Collaborator

tyler36 commented Nov 1, 2023

Is there a specific problem with solr dashboard on HTTPS? Or is it just flaky?

I was able to get it working by updating docker-compose.solr.yaml on Chrome:

      - HTTP_EXPOSE=8983:8983
+     - HTTPS_EXPOSE=8984:8983

image

@rfay
Copy link
Member

rfay commented Nov 1, 2023

The reason that solr has not provided HTTPS in the past is that it always inappropriately redirected and was basically broken, at least on some browsers. What browser are you using? It's possible that Solr itself has solved this problem.

I think the issue is that the Solr UI didn't look at the x-forwarded-proto, so assumed it was talking http, and messed up there.

I'm OK with this if the problem has gone away, but it was persistent for years, so needs wide testing on a variety of OSs and browsers, and will need changes to the automated tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants