[web2py] Re: Houston, Houston, the rocket lost contact!
new rocket launched to trunk. On May 3, 1:39 pm, Timothy Farrell wrote: > Negative. The latter code is unrelated (though a similar style). > However, I have changed it to be consistent in the patch I sent to > Massimo. Look for it in an upcoming commit. > > -tim > > On 5/3/2010 1:33 PM, Jonathan Lundell wrote: > > > On May 3, 2010, at 9:41 AM, Timothy Farrell wrote: > > >> So changing line 86 from ssl = None to ssl = False should take care of it. > > > This pattern is repeated around line 130; that might be why mr freeze > > didn't see a change.
Re: [web2py] Re: Houston, Houston, the rocket lost contact!
Negative. The latter code is unrelated (though a similar style). However, I have changed it to be consistent in the patch I sent to Massimo. Look for it in an upcoming commit. -tim On 5/3/2010 1:33 PM, Jonathan Lundell wrote: On May 3, 2010, at 9:41 AM, Timothy Farrell wrote: So changing line 86 from ssl = None to ssl = False should take care of it. This pattern is repeated around line 130; that might be why mr freeze didn't see a change.
Re: [web2py] Re: Houston, Houston, the rocket lost contact!
On May 3, 2010, at 9:41 AM, Timothy Farrell wrote: > So changing line 86 from ssl = None to ssl = False should take care of it. This pattern is repeated around line 130; that might be why mr freeze didn't see a change.
[web2py] Re: Houston, Houston, the rocket lost contact!
I'll wait for the patch. Massimo On May 3, 12:26 pm, Timothy Farrell wrote: > Good enough for me. Let's call that the fix. > > --tim > > On 5/3/2010 12:02 PM, mr.freeze wrote: > > > No luck. Changing it has no effect. The debug still prints: > > > ssl: None > > secure: False > > > If I change at line 83 to: > > try: > > import ssl > > has_ssl = True > > except ImportError: > > has_ssl = False > > > and line 97 to: > > self.ssl = has_ssl and isinstance(self.socket, ssl.SSLSocket) > > > it works. > > > On May 3, 11:41 am, Timothy Farrell wrote: > > >> So changing line 86 from ssl = None to ssl = False should take care of it. > > >> -tim > > >> On 5/3/2010 10:58 AM, Iceberg wrote: > > >>> I got same output as Nathan (Mr. Freeze). > > >>> The ssl=None seems because my python2.5 on Windows contains no ssl > >>> module at all. > > >>> On May3, 11:30pm, "mr.freeze" wrote: > > I get: > ssl: None > secure: False > > On May 3, 8:11 am, Timothy Farrell wrote: > > > To help me debug this, would one of you do the following: > > > Add some code at line 99: > > > print "ssl: ", self.ssl > > print "secure: ", self.secure > > > These two values should, in all cases be the same. If they are not, > > you'll get a 400. If you're seeing this error, it means one or the > > other is not what it should be. Please tell me which one. > > > Thanks, > > -tim > > > On 5/3/2010 7:54 AM, Timothy Farrell wrote: > > >> The main change between the two versions is where it applies the SSL > >> connection and adds a check to see if that connection isn't there when > >> it should be. I've updated to the latest hg and I'm not seeing what > >> you guys are seeing. > > >> Are any of you running HTTPS? > > >> Rocket does not support IPV6 yet. > > >> -tim > > >> On 5/2/2010 12:10 PM, Iceberg wrote: > > >>> Sorry, Cjrh, the tip doesn't help. To summarize: > > >>> 1) Bothhttp://localhost:8000andhttp://127.0.0.1:8000workwhenI > >>> am using old rocket.py, and I just double confirm my hosts file > >>> contains "127.0.0.1 localhost" since long long ago. > >>> 2) Neitherhttp://localhost:8000norhttp://127.0.0.1:8000workswith > >>> latest rocket.py > > >>> Actually I took a glance into the diff between latest two "rockets". > >>> They look significantly different, but I could not trace down to > >>> certain line yet. It is rocket science after all. :-) > > >>> Sos, Sos... > > >>> On May2日, 5:57am, mdipierro wrote: > > @Iceberg, does the suggestion below fix the problem? > > @Tim. Does Rocket support IPV6 addresses? > > Massimo
Re: [web2py] Re: Houston, Houston, the rocket lost contact!
Good enough for me. Let's call that the fix. --tim On 5/3/2010 12:02 PM, mr.freeze wrote: No luck. Changing it has no effect. The debug still prints: ssl: None secure: False If I change at line 83 to: try: import ssl has_ssl = True except ImportError: has_ssl = False and line 97 to: self.ssl = has_ssl and isinstance(self.socket, ssl.SSLSocket) it works. On May 3, 11:41 am, Timothy Farrell wrote: So changing line 86 from ssl = None to ssl = False should take care of it. -tim On 5/3/2010 10:58 AM, Iceberg wrote: I got same output as Nathan (Mr. Freeze). The ssl=None seems because my python2.5 on Windows contains no ssl module at all. On May3, 11:30pm, "mr.freeze"wrote: I get: ssl: None secure: False On May 3, 8:11 am, Timothy Farrellwrote: To help me debug this, would one of you do the following: Add some code at line 99: print "ssl: ", self.ssl print "secure: ", self.secure These two values should, in all cases be the same. If they are not, you'll get a 400. If you're seeing this error, it means one or the other is not what it should be. Please tell me which one. Thanks, -tim On 5/3/2010 7:54 AM, Timothy Farrell wrote: The main change between the two versions is where it applies the SSL connection and adds a check to see if that connection isn't there when it should be. I've updated to the latest hg and I'm not seeing what you guys are seeing. Are any of you running HTTPS? Rocket does not support IPV6 yet. -tim On 5/2/2010 12:10 PM, Iceberg wrote: Sorry, Cjrh, the tip doesn't help. To summarize: 1) Bothhttp://localhost:8000andhttp://127.0.0.1:8000workwhenI am using old rocket.py, and I just double confirm my hosts file contains "127.0.0.1 localhost" since long long ago. 2) Neitherhttp://localhost:8000norhttp://127.0.0.1:8000workswith latest rocket.py Actually I took a glance into the diff between latest two "rockets". They look significantly different, but I could not trace down to certain line yet. It is rocket science after all. :-) Sos, Sos... On May2日, 5:57am, mdipierro wrote: @Iceberg, does the suggestion below fix the problem? @Tim. Does Rocket support IPV6 addresses? Massimo
[web2py] Re: Houston, Houston, the rocket lost contact!
No luck. Changing it has no effect. The debug still prints: ssl: None secure: False If I change at line 83 to: try: import ssl has_ssl = True except ImportError: has_ssl = False and line 97 to: self.ssl = has_ssl and isinstance(self.socket, ssl.SSLSocket) it works. On May 3, 11:41 am, Timothy Farrell wrote: > So changing line 86 from ssl = None to ssl = False should take care of it. > > -tim > > On 5/3/2010 10:58 AM, Iceberg wrote: > > > I got same output as Nathan (Mr. Freeze). > > > The ssl=None seems because my python2.5 on Windows contains no ssl > > module at all. > > > On May3, 11:30pm, "mr.freeze" wrote: > > >> I get: > >> ssl: None > >> secure: False > > >> On May 3, 8:11 am, Timothy Farrell wrote: > > >>> To help me debug this, would one of you do the following: > > >>> Add some code at line 99: > > >>> print "ssl: ", self.ssl > >>> print "secure: ", self.secure > > >>> These two values should, in all cases be the same. If they are not, > >>> you'll get a 400. If you're seeing this error, it means one or the > >>> other is not what it should be. Please tell me which one. > > >>> Thanks, > >>> -tim > > >>> On 5/3/2010 7:54 AM, Timothy Farrell wrote: > > The main change between the two versions is where it applies the SSL > connection and adds a check to see if that connection isn't there when > it should be. I've updated to the latest hg and I'm not seeing what > you guys are seeing. > > Are any of you running HTTPS? > > Rocket does not support IPV6 yet. > > -tim > > On 5/2/2010 12:10 PM, Iceberg wrote: > > > Sorry, Cjrh, the tip doesn't help. To summarize: > > > 1) Bothhttp://localhost:8000andhttp://127.0.0.1:8000workwhenI > > am using old rocket.py, and I just double confirm my hosts file > > contains "127.0.0.1 localhost" since long long ago. > > 2) Neitherhttp://localhost:8000norhttp://127.0.0.1:8000workswith > > latest rocket.py > > > Actually I took a glance into the diff between latest two "rockets". > > They look significantly different, but I could not trace down to > > certain line yet. It is rocket science after all. :-) > > > Sos, Sos... > > > On May2日, 5:57am, mdipierro wrote: > > >> @Iceberg, does the suggestion below fix the problem? > > >> @Tim. Does Rocket support IPV6 addresses? > > >> Massimo
Re: [web2py] Re: Houston, Houston, the rocket lost contact!
So changing line 86 from ssl = None to ssl = False should take care of it. -tim On 5/3/2010 10:58 AM, Iceberg wrote: I got same output as Nathan (Mr. Freeze). The ssl=None seems because my python2.5 on Windows contains no ssl module at all. On May3, 11:30pm, "mr.freeze" wrote: I get: ssl: None secure: False On May 3, 8:11 am, Timothy Farrell wrote: To help me debug this, would one of you do the following: Add some code at line 99: print "ssl: ", self.ssl print "secure: ", self.secure These two values should, in all cases be the same. If they are not, you'll get a 400. If you're seeing this error, it means one or the other is not what it should be. Please tell me which one. Thanks, -tim On 5/3/2010 7:54 AM, Timothy Farrell wrote: The main change between the two versions is where it applies the SSL connection and adds a check to see if that connection isn't there when it should be. I've updated to the latest hg and I'm not seeing what you guys are seeing. Are any of you running HTTPS? Rocket does not support IPV6 yet. -tim On 5/2/2010 12:10 PM, Iceberg wrote: Sorry, Cjrh, the tip doesn't help. To summarize: 1) Bothhttp://localhost:8000andhttp://127.0.0.1:8000workwhen I am using old rocket.py, and I just double confirm my hosts file contains "127.0.0.1 localhost" since long long ago. 2) Neitherhttp://localhost:8000norhttp://127.0.0.1:8000workswith latest rocket.py Actually I took a glance into the diff between latest two "rockets". They look significantly different, but I could not trace down to certain line yet. It is rocket science after all. :-) Sos, Sos... On May2日, 5:57am, mdipierrowrote: @Iceberg, does the suggestion below fix the problem? @Tim. Does Rocket support IPV6 addresses? Massimo
[web2py] Re: Houston, Houston, the rocket lost contact!
I got same output as Nathan (Mr. Freeze). The ssl=None seems because my python2.5 on Windows contains no ssl module at all. On May3, 11:30pm, "mr.freeze" wrote: > I get: > ssl: None > secure: False > > On May 3, 8:11 am, Timothy Farrell wrote: > > > > > To help me debug this, would one of you do the following: > > > Add some code at line 99: > > > print "ssl: ", self.ssl > > print "secure: ", self.secure > > > These two values should, in all cases be the same. If they are not, > > you'll get a 400. If you're seeing this error, it means one or the > > other is not what it should be. Please tell me which one. > > > Thanks, > > -tim > > > On 5/3/2010 7:54 AM, Timothy Farrell wrote: > > > > The main change between the two versions is where it applies the SSL > > > connection and adds a check to see if that connection isn't there when > > > it should be. I've updated to the latest hg and I'm not seeing what > > > you guys are seeing. > > > > Are any of you running HTTPS? > > > > Rocket does not support IPV6 yet. > > > > -tim > > > > On 5/2/2010 12:10 PM, Iceberg wrote: > > >> Sorry, Cjrh, the tip doesn't help. To summarize: > > > >> 1) Bothhttp://localhost:8000andhttp://127.0.0.1:8000workwhen I > > >> am using old rocket.py, and I just double confirm my hosts file > > >> contains "127.0.0.1 localhost" since long long ago. > > >> 2) Neitherhttp://localhost:8000norhttp://127.0.0.1:8000workswith > > >> latest rocket.py > > > >> Actually I took a glance into the diff between latest two "rockets". > > >> They look significantly different, but I could not trace down to > > >> certain line yet. It is rocket science after all. :-) > > > >> Sos, Sos... > > > >> On May2日, 5:57am, mdipierro wrote: > > >>> @Iceberg, does the suggestion below fix the problem? > > > >>> @Tim. Does Rocket support IPV6 addresses? > > > >>> Massimo
[web2py] Re: Houston, Houston, the rocket lost contact!
I get: ssl: None secure: False On May 3, 8:11 am, Timothy Farrell wrote: > To help me debug this, would one of you do the following: > > Add some code at line 99: > > print "ssl: ", self.ssl > print "secure: ", self.secure > > These two values should, in all cases be the same. If they are not, > you'll get a 400. If you're seeing this error, it means one or the > other is not what it should be. Please tell me which one. > > Thanks, > -tim > > On 5/3/2010 7:54 AM, Timothy Farrell wrote: > > > The main change between the two versions is where it applies the SSL > > connection and adds a check to see if that connection isn't there when > > it should be. I've updated to the latest hg and I'm not seeing what > > you guys are seeing. > > > Are any of you running HTTPS? > > > Rocket does not support IPV6 yet. > > > -tim > > > On 5/2/2010 12:10 PM, Iceberg wrote: > >> Sorry, Cjrh, the tip doesn't help. To summarize: > > >> 1) Bothhttp://localhost:8000andhttp://127.0.0.1:8000work when I > >> am using old rocket.py, and I just double confirm my hosts file > >> contains "127.0.0.1 localhost" since long long ago. > >> 2) Neitherhttp://localhost:8000norhttp://127.0.0.1:8000works with > >> latest rocket.py > > >> Actually I took a glance into the diff between latest two "rockets". > >> They look significantly different, but I could not trace down to > >> certain line yet. It is rocket science after all. :-) > > >> Sos, Sos... > > >> On May2日, 5:57am, mdipierro wrote: > >>> @Iceberg, does the suggestion below fix the problem? > > >>> @Tim. Does Rocket support IPV6 addresses? > > >>> Massimo > > >>> On May 1, 4:31 pm, cjrh wrote: > > On May 1, 1:36 pm, Iceberg wrote: > > please visit: > > http://127.0.0.1:8000 > and > > The console output is as usual. But we only get "400 Bad Request" > > fromhttp://localhost:8000 > http://mwolk.com/blog/localhost-not-working-but-127001-does/
Re: [web2py] Re: Houston, Houston, the rocket lost contact!
To help me debug this, would one of you do the following: Add some code at line 99: print "ssl: ", self.ssl print "secure: ", self.secure These two values should, in all cases be the same. If they are not, you'll get a 400. If you're seeing this error, it means one or the other is not what it should be. Please tell me which one. Thanks, -tim On 5/3/2010 7:54 AM, Timothy Farrell wrote: The main change between the two versions is where it applies the SSL connection and adds a check to see if that connection isn't there when it should be. I've updated to the latest hg and I'm not seeing what you guys are seeing. Are any of you running HTTPS? Rocket does not support IPV6 yet. -tim On 5/2/2010 12:10 PM, Iceberg wrote: Sorry, Cjrh, the tip doesn't help. To summarize: 1) Both http://localhost:8000 and http://127.0.0.1:8000 work when I am using old rocket.py, and I just double confirm my hosts file contains "127.0.0.1 localhost" since long long ago. 2) Neither http://localhost:8000 nor http://127.0.0.1:8000 works with latest rocket.py Actually I took a glance into the diff between latest two "rockets". They look significantly different, but I could not trace down to certain line yet. It is rocket science after all. :-) Sos, Sos... On May2日, 5:57am, mdipierro wrote: @Iceberg, does the suggestion below fix the problem? @Tim. Does Rocket support IPV6 addresses? Massimo On May 1, 4:31 pm, cjrh wrote: On May 1, 1:36 pm, Iceberg wrote: please visit: http://127.0.0.1:8000 and The console output is as usual. But we only get "400 Bad Request" fromhttp://localhost:8000 http://mwolk.com/blog/localhost-not-working-but-127001-does/
Re: [web2py] Re: Houston, Houston, the rocket lost contact!
The main change between the two versions is where it applies the SSL connection and adds a check to see if that connection isn't there when it should be. I've updated to the latest hg and I'm not seeing what you guys are seeing. Are any of you running HTTPS? Rocket does not support IPV6 yet. -tim On 5/2/2010 12:10 PM, Iceberg wrote: Sorry, Cjrh, the tip doesn't help. To summarize: 1) Both http://localhost:8000 and http://127.0.0.1:8000 work when I am using old rocket.py, and I just double confirm my hosts file contains "127.0.0.1 localhost" since long long ago. 2) Neither http://localhost:8000 nor http://127.0.0.1:8000 works with latest rocket.py Actually I took a glance into the diff between latest two "rockets". They look significantly different, but I could not trace down to certain line yet. It is rocket science after all. :-) Sos, Sos... On May2日, 5:57am, mdipierro wrote: @Iceberg, does the suggestion below fix the problem? @Tim. Does Rocket support IPV6 addresses? Massimo On May 1, 4:31 pm, cjrh wrote: On May 1, 1:36 pm, Iceberg wrote: please visit: http://127.0.0.1:8000 and The console output is as usual. But we only get "400 Bad Request" fromhttp://localhost:8000 http://mwolk.com/blog/localhost-not-working-but-127001-does/
[web2py] Re: Houston, Houston, the rocket lost contact!
Sorry, Cjrh, the tip doesn't help. To summarize: 1) Both http://localhost:8000 and http://127.0.0.1:8000 work when I am using old rocket.py, and I just double confirm my hosts file contains "127.0.0.1 localhost" since long long ago. 2) Neither http://localhost:8000 nor http://127.0.0.1:8000 works with latest rocket.py Actually I took a glance into the diff between latest two "rockets". They look significantly different, but I could not trace down to certain line yet. It is rocket science after all. :-) Sos, Sos... On May2日, 5:57am, mdipierro wrote: > @Iceberg, does the suggestion below fix the problem? > > @Tim. Does Rocket support IPV6 addresses? > > Massimo > > On May 1, 4:31 pm, cjrh wrote: > > > > > On May 1, 1:36 pm, Iceberg wrote: > > > > please visit: > > > http://127.0.0.1:8000 > > > and > > > > The console output is as usual. But we only get "400 Bad Request" > > > fromhttp://localhost:8000 > > >http://mwolk.com/blog/localhost-not-working-but-127001-does/
[web2py] Re: Houston, Houston, the rocket lost contact!
@Iceberg, does the suggestion below fix the problem? @Tim. Does Rocket support IPV6 addresses? Massimo On May 1, 4:31 pm, cjrh wrote: > On May 1, 1:36 pm, Iceberg wrote: > > > please visit: > > http://127.0.0.1:8000 > > and > > > The console output is as usual. But we only get "400 Bad Request" > > fromhttp://localhost:8000 > > http://mwolk.com/blog/localhost-not-working-but-127001-does/
[web2py] Re: Houston, Houston, the rocket lost contact!
On May 1, 1:36 pm, Iceberg wrote: > please visit: > http://127.0.0.1:8000 and > The console output is as usual. But we only get "400 Bad Request" > fromhttp://localhost:8000 http://mwolk.com/blog/localhost-not-working-but-127001-does/
