-
Notifications
You must be signed in to change notification settings - Fork 49
https://mysite.dev returns error #116
Comments
There shouldn't be more configuration required, as long as Prax is listening on :20558 You hit the dreadful bug that makes the host non determinable (prax can't proxy without a host to like the app to). Could you inspect the request sent from the browser? That would help debug. |
So I was wrong earlier when I said prax would serve no https requests - it does handle some https pages just fine. What I think is the issue is that the pages that error have a force_ssl = true. When it attempts to redirect to https is goes into an infinite redirect loop - as if it can't tell that the https protocol was already in use. Here's the request headers:
Development Log:
... repeated until browser gives up with "The page isn't redirecting properly" . |
SSL never reaches the application itself. Prax will handle the HTTPS part and only tells the application about it with the Prax must intercept/handle the HTTPS otherwise it wouldn't be able to know which application or port to proxy the request to. |
Started prax with "prax start -f" - everything runs fine until I navigate into a secure section of the site that uses https and this error is returned:
E, [2015-03-07T14:19:52.802521 #3654] ERROR -- : ArgumentError: bad argument (expected URI object or URI string)
/home/jimmy/.rbenv/versions/2.0.0-p481/lib/ruby/2.0.0/uri/common.rb:998:in
URI' /opt/prax/lib/prax/request.rb:136:in
determine_host'/opt/prax/lib/prax/request.rb:75:in
host' /opt/prax/lib/prax/handler.rb:66:in
app_name'/opt/prax/lib/prax/handler.rb:17:in
handle' /opt/prax/lib/prax.rb:21:in
perform'/opt/prax/lib/prax/microworker.rb:84:in
block in work' /opt/prax/lib/prax/microworker.rb:77:in
each'/opt/prax/lib/prax/microworker.rb:77:in
work' /opt/prax/lib/prax/microworker.rb:63:in
block in spawn'I, [2015-03-07T14:19:52.802596 #3654] INFO -- : Respawning failed worker
This is on a fresh install of Ubuntu 14.04 LTS,. Is there some addition setup required to use ssl?
The text was updated successfully, but these errors were encountered: