This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Shane Smith
Recipients Shane Smith
Date 2020-01-04.18:26:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1578162394.57.0.362691529673.issue39211@roundup.psfhosted.org>
In-reply-to
Content
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 http.server 8000

and it would default to whatever IP address was available.  Now, in order for it to function at all (not return "This site can’t be reached" in Chrome), I have to bind it to a specific IP address (say, 127.0.0.1, sticking with the docs example).

> python -m http.server 8000 --bind 127.0.0.1

At which point it works fine.  So it's still quite usable for this purpose, though I was surprised and -simple as the solution is- the solution is less simple when you don't know it!

Was this an intended change?  Something something security, perhaps?  If so, should it be noted in the "What's new" of the docs?  And of course, there's always the slight possibility that some aspect of Windows or Chrome behavior changed, but based on the termal's response I don't think that's the case.

Thanks,
History
Date User Action Args
2020-01-04 18:26:34Shane Smithsetrecipients: + Shane Smith
2020-01-04 18:26:34Shane Smithsetmessageid: <1578162394.57.0.362691529673.issue39211@roundup.psfhosted.org>
2020-01-04 18:26:34Shane Smithlinkissue39211 messages
2020-01-04 18:26:33Shane Smithcreate