-
Notifications
You must be signed in to change notification settings - Fork 80
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
Listen for both http and https with lineman run
#310
base: master
Are you sure you want to change the base?
Conversation
@jasonkarns @davemo either of you have a chance to review / test this a bit? The impact is hard to read for me b/c of the indent shift |
Okay, reviewing:
The last step just hangs forever. Is there anything you can do to make it redirect if you hit the app on the HTTPS port to redirect to the https protocol? |
Right because https and http listen on different ports but both are configurable. http defaults to 8443 as you've seen. |
Right, I realize that, but if someone wants to hit the https version of the page and they lazily type in |
Ahhh, I see what you're saying. I can look into that. Do you think this PR still adds a measurable improvement and could be merged before adding a redirect enhancement? |
Yeah, probably, but I do worry about the silly support issues the redirect thing will elicit. I am also worried about what speed and memory overhead this introduces, since it's always on |
Heh, Yea, I thought about that too. What do you think about an 'enableHttps' option? |
+1 for an opt-in option On Thu, Aug 14, 2014 at 12:38 PM, Jonathan Worent
|
Was this obviated by #352? |
I think this would still be necessary. #352, afaict, only enables proxied requests to hit an https endpoint. It doesn't make lineman's server listen for https traffic. |
Referencing issue #309.
This is a simple way to handle https during development. It will listen for https traffic along side http traffic via a configurable port.