I'm with the Solr project. Solr runs in Jetty. It is not embedded, the
startup script runs start.jar.
I'm trying to help one of our users with a problem. They have a proxy
server handling TLS, Solr listens without encryption.
Here's the bug report on Solr:
https://issues.apache.org/jira/browse/SOLR-16200/
If they access the admin UI via the proxy server using https on the
/solr URL path, where the webapp lives, everything's fine. All links
stay https even though Solr is listening without encryption. But if
they access the root URL with https, Jetty is redirecting them to a URL
that is hardcoded as http://server:port/solr/ instead of preserving the
https:// that was used to access it, which doesn't work, because the
proxy is configured with TLS. I have reproduced the problem. I found a
way to work around the issue with my proxy server, but it would be
really nice if that was not required.
Is there any way in the jetty config to have it preserve the URL scheme
when it redirects? If it were to redirect to a relative path of /solr
instead of an absolute URL that contains http:// that would fix it.
What information do I need to provide to help troubleshoot and find a fix?
Thanks,
Shawn
_______________________________________________
jetty-users mailing list
jetty-users@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users