As it turned out, if you started the php server with "php -S localhost:80" the server will be started with ipv6 support only!
To access it via ipv4, you need to change the start up command like so: "php -S 127.0.0."which starts server in ipv4 mode only.
As with any other bogus packets, they may be malicious and any problems they might cause can be avoided by applying bogon filtering.
The releases of the My SQL database differentiate between the use of the hostname localhost and the use of the addresses 127.0.0.1 and ::1.
For example, a locally installed website may be accessed from a web browser by the URL to display its home page.
I painfully experienced behaviour that I can't seem to find documented here so I wanted to save everyone from repeating my mistake by giving the following heads up: When starting php -S on a mac (in my case mac OS Sierra) to host a local server, I had trouble with connecting from legacy Java.
IPv4 network standards reserve the entire 127.0.0.0/8 address block for loopback purposes.
That means any packet sent to any of those addresses (127.0.0.1 through 127.255.255.255) is looped back.
Learn more, including about available controls: Cookies Policy.
[Thu Jul 21 2011] ::144 GET /- Request read [Thu Jul 21 2011] ::146 GET / - Request read [Thu Jul 21 2011] ::147 GET /- Request read [Thu Jul 21 2011] ::148 GET /- Request read [Thu Jul 21 2011] ::149 GET /- Request read In order to set project specific configuration options, simply add a file to your project, and then run the built-in server with this flag:php -S localhost:8000 -c This is especially helpful for settings that cannot be set at runtime (ini_set()).When using localhost as the destination in a client connector interface of an application, the My SQL application programming interface connects to the database using a Unix domain socket, while a TCP connection via the loopback interface requires the direct use of the explicit address.One notable exception to the use of the 127.0.0.0/8 network addresses is their use in Multiprotocol Label Switching (MPLS) traceroute error detection, in which their property of not being routable provides a convenient means to avoid delivery of faulty packets to end users.Such packets are never passed to any network interface controller (NIC) or hardware device driver and must not appear outside of a computing system, or be routed by any router.