-
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
bioprotocols.org http vs https URLs #167
Comments
Note: This also affects https://labop.io On my machine, only the latter works. |
At time of writing, neither http://bioprotocols.github.io nor https://bioprotocols.github.io do a redirect. Just gives a 404 not found. |
I looked into this, and it is not necessarily a bug. We are hosting a project page for labop which is http://bioprotocols.github.io/labop, but we are not hosting an organization page. The org page would live at the base URL. We have a README.md that is serving that purpose at https://github.com/Bioprotocols, but I think we’d need a gh-pages site parallel to it to have a base URL site.
… On Feb 19, 2023, at 3:25 PM, Timothy R. Fallon, PhD ***@***.***> wrote:
At time of writing, neither http://bioprotocols.github.io nor https://bioprotocols.github.io do a redirect. Just gives a 404 not found.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
I fixed the redirect for http://bioprotocols.github.io/ and https://bioprotocols.github.io/. I'll leave this issue open because we still don't have https working for Bioprotocols.org. |
Putting this issue here as seems as good a place as any!
Currently, http://bioprotocols.org , redirects to https://bioprotocols.github.io/labop/
But, https://bioprotocols.org doesn't work, i.e. it is a failed redirect.
Based on some checks of the hosting documentation by @jakebeal , it's not possible to do
https
forwarding with the current registrar/host. So, if people really want ahttps
redirect from that domain, might be a minor project.The text was updated successfully, but these errors were encountered: