-
Notifications
You must be signed in to change notification settings - Fork 5
Redirect HTTPS traffic to HTTP #34
Comments
We can do this by editing our nginx.conf. I can get this setup for both site/api and document it. |
wait, why is nginx running? You can do port forwarding w/ iptables
|
No nginx running! We're using iptables - this was when I thought we were going to be having both the API/website on the same server. |
ah, perfect. Ok, well in order to get cloudflare to work with ssl, I think you need to also forward to 443 |
@ethanresnick: are there any subdomains in the techatnyu.org website that needs to be using SSL? We can remove the api.techatnyu.org b/c that's the only one that comes to mind that needs to run using SSL. I don't think we should using cloud for tnyu.org yet. I get what you mean! Yeah I'll just do a redirect |
@AbhiAgarwal I think we should assume that, at some point, we may have other subdomains on techatnyu.org that use SSL. So cloudflare should be set up to support that, if possible. But, for right now, I was just suggesting doing a simple 301 redirect to |
No description provided.
The text was updated successfully, but these errors were encountered: