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
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
I get:
ssl: None
secure: False
On May 3, 8:11 am, Timothy Farrell tfarr...@swgen.com 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
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 nat...@freezable.com wrote:
I get:
ssl: None
secure: False
On May 3, 8:11 am, Timothy Farrell tfarr...@swgen.com wrote:
To help me
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.freezenat...@freezable.com
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
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
I'll wait for the patch.
Massimo
On May 3, 12:26 pm, Timothy Farrell tfarr...@swgen.com 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
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.
new rocket launched to trunk.
On May 3, 1:39 pm, Timothy Farrell tfarr...@swgen.com 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
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
On May 1, 1:36 pm, Iceberg iceb...@21cn.com 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/
@Iceberg, does the suggestion below fix the problem?
@Tim. Does Rocket support IPV6 addresses?
Massimo
On May 1, 4:31 pm, cjrh caleb.hatti...@gmail.com wrote:
On May 1, 1:36 pm, Iceberg iceb...@21cn.com wrote:
please visit:
http://127.0.0.1:8000
and
The console
13 matches
Mail list logo
