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

HTTPS not working behind reverse proxy #12

Open
Chovin opened this issue Mar 3, 2021 · 2 comments
Open

HTTPS not working behind reverse proxy #12

Chovin opened this issue Mar 3, 2021 · 2 comments

Comments

@Chovin
Copy link

Chovin commented Mar 3, 2021

possible issues contributing to this:

  • web_asset_store.xml template has http:// hardcoded into it
  • server.py lines 204 and 330 hardcodes http:// and the settings.py port. It may be better to pull this information from the request itself.

I don't think fixing these is enough to get https working for the Specify app (at least v6) as an error still occurs after fixing these when trying to use the https url with the Specify app.

@misilot
Copy link

misilot commented Feb 27, 2023

This is still an issue. As when you try to use this with specify7 (all-in-one docker-compose example) behind HTTPS, the urls are generated as

<?xml version="1.0" encoding="UTF-8"?>
<urls>
    <url type="read"><![CDATA[http://SERVERNAME:443/fileget]]></url>
    <url type="write"><![CDATA[http://SERVERNAME:443/fileupload]]></url>
    <url type="delete"><![CDATA[http://SERVERNAME:443/filedelete]]></url>
    <url type="getmetadata"><![CDATA[http://SERVERNAME:443/getmetadata]]></url>
    <url type="testkey">http://SERVERNAME:443/testkey</url>
</urls>

Which mixing http:// and port 443 doesn't mix.

@misilot
Copy link

misilot commented Feb 27, 2023

I did find the gist in the HTTPS section, and that did work.

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

No branches or pull requests

2 participants