[issue39211] Change in http.server default IP behavior?

Shane added the comment: Based on my understanding, your fix should do it. -- stage: -> resolved status: open -> closed ___ Python tracker ___

[issue39211] Change in http.server default IP behavior?

Jason R. Coombs added the comment: Other than addressing issue38907, is there anything else to be done here? In GH-17851, I've proposed a surgical fix to address the issue with IPv4 being unbound on Windows. -- ___ Python tracker

[issue39211] Change in http.server default IP behavior?

Shane added the comment: Jason, thank you for the primer. > Nevertheless, when I tried the same thing on my Windows machine, I got a > different outcome. The server bound to [::0] but was unreachable on > http://127.0.0.1:8000. Perhaps it's an issue with IPv4 addresses in general for

[issue39211] Change in http.server default IP behavior?

Jason R. Coombs added the comment: Indeed, if I apply this patch: ``` diff --git a/Lib/http/server.py b/Lib/http/server.py index 47a4fcf9a6..de995ae4b9 100644 --- a/Lib/http/server.py +++ b/Lib/http/server.py @@ -1246,6 +1246,11 @@ def test(HandlerClass=BaseHTTPRequestHandler, """

[issue39211] Change in http.server default IP behavior?

Jason R. Coombs added the comment: > It's the addition of flags=socket.AI_PASSIVE on Lib/http/server.py:1233 > that's causing this. Can you elaborate? What is it causing? I can see that flag was added in

[issue39211] Change in http.server default IP behavior?

Jason R. Coombs added the comment: First, a quick primer in IP: - Addresses are written as :::::::, but any single span of zeros can be written as ::, so `::` is all zeros and `::1` is the same as :::::::0001. - ::1 is the local

[issue39211] Change in http.server default IP behavior?

SilentGhost added the comment: It's the addition of flags=socket.AI_PASSIVE on Lib/http/server.py:1233 that's causing this. I think this also breaks for IPv4 sockets. -- components: +Library (Lib) keywords: +3.8regression nosy: +SilentGhost stage: -> needs patch

[issue39211] Change in http.server default IP behavior?

Shane added the comment: A small update: Using the direct invocation: > python -m http.server 8000 Serving HTTP on :: port 8080 (http://[::]:8080/) ... Is NOT accessible at the following addresses: http://[::]:8080/ # most surprising, because this is where it tells you to go http://:8080/

[issue39211] Change in http.server default IP behavior?

Shane added the comment: For the basic invocation: >python -m http.server 8080 Serving HTTP on :: port 8080 (http://[::]:8080/) ... It just sits there, because I can't access it (http://[::]:8080/ is not a valid address, so far as I know, and inserting my IP address doesn't find it either).

[issue39211] Change in http.server default IP behavior?

Change by Karthikeyan Singaravelan : -- nosy: +jaraco ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39211] Change in http.server default IP behavior?

Karthikeyan Singaravelan added the comment: Can you please paste the output of http.server as in the port and address printed as a log when started for different commands? As I can see from the history the binding process was changed to include IPv6 as default :

[issue39211] Change in http.server default IP behavior?

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39211] Change in http.server default IP behavior?

New submission from Shane : It seems to me that the direct invocation behavior for http.server changed, probably with Python 3.8 (I'm currently using 3.8.1 on Windows 10). On 3.7.X I was able to use it as described in the docs (https://docs.python.org/3/library/http.server.html) > python -m

[issue39211] Change in http.server default IP behavior?

Change by Shane : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: