the browser does not know the server's IP address associated to the URL. Hence it goes to the ISP for the server's address.
The browser goes to the OS and asks for an IP address associated with a particular hostname. If the OS can't resolve it itself (by using cache or local hosts file) it goes to a default DNS server configured in the system.
Where did you find this request/response diagram? It's a bit wrong.
An HTTP request consists of a start line, optional headers and optional body. HTTP method, path (request target) and HTTP version are part of the start line, not headers.
A host can be an IP address, a host name or a domain. It's not a URL. The URL must at least consist of a scheme and a path to a resource.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The browser goes to the OS and asks for an IP address associated with a particular hostname. If the OS can't resolve it itself (by using cache or local hosts file) it goes to a default DNS server configured in the system.
Where did you find this request/response diagram? It's a bit wrong.
An HTTP request consists of a start line, optional headers and optional body. HTTP method, path (request target) and HTTP version are part of the start line, not headers.
A host can be an IP address, a host name or a domain. It's not a URL. The URL must at least consist of a scheme and a path to a resource.