Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I understand that any World Wide Web interaction works this way: Stage 1: Client (human or software) ⟶ User agent ⟶ HTTP/S web-server request (with an unresolved domain) Stage 2: ISP-initiated Rou...
Question
web
#5: Post undeleted
by
Alexei
·
2020-10-25T17:26:50Z (about 4 years ago)
#4: Post deleted
by
Alexei
·
2020-10-25T17:26:46Z (about 4 years ago)
#3: Question closed
by
Lundin
·
2020-09-08T09:15:08Z (about 4 years ago)
#2: Post edited
How do World Wide Web interactions work in a general level?
- How do World Wide Web interactions happen in a general level?
- I understand that any World Wide Web interaction works this way:
- * **Stage 1:** *Client* (human or software) ⟶ *User agent* ⟶ *HTTP/S web-server request* (with an unresolved domain)
- * **Stage 2:** *ISP-initiated Routing software* ⟶ *DNS server* (one, or two or more until resolve) ⟶ *DNS resolve*
- * **Stage 3:** *A web Server which is part of a server environment of a computer system with the "resolved" IP address processes the server request*
- * **Stage 4:** *HTTP/S web Server response* (with a resolved domain) ⟶ *Server-initiated routing software* ⟶ *Client* (human or software)
- Regarding stage 2, I understand that **some** ISP routing software will try to lookup/resolve/translate a given domain with a given IP address "somewhere in the internet" and because that IP address can be associated with one or more DNS servers, the routing software would have to go through all DNS servers in the world until it reaches one which can "resolve" or "translate" the domain to an IP address and then the rest of the process will continue.
How do World Wide Web interactions work in a general level (was my general description correct or "enough-accurate")?
- I understand that any World Wide Web interaction works this way:
- * **Stage 1:** *Client* (human or software) ⟶ *User agent* ⟶ *HTTP/S web-server request* (with an unresolved domain)
- * **Stage 2:** *ISP-initiated Routing software* ⟶ *DNS server* (one, or two or more until resolve) ⟶ *DNS resolve*
- * **Stage 3:** *A web Server which is part of a server environment of a computer system with the "resolved" IP address processes the server request*
- * **Stage 4:** *HTTP/S web Server response* (with a resolved domain) ⟶ *Server-initiated routing software* ⟶ *Client* (human or software)
- Regarding stage 2, I understand that **some** ISP routing software will try to lookup/resolve/translate a given domain with a given IP address "somewhere in the internet" and because that IP address can be associated with one or more DNS servers, the routing software would have to go through all DNS servers in the world until it reaches one which can "resolve" or "translate" the domain to an IP address and then the rest of the process will continue.
- How do World Wide Web interactions happen in a general level (was my general description correct or "enough-accurate")?
#1: Initial revision
How do World Wide Web interactions work in a general level?
I understand that any World Wide Web interaction works this way: * **Stage 1:** *Client* (human or software) ⟶ *User agent* ⟶ *HTTP/S web-server request* (with an unresolved domain) * **Stage 2:** *ISP-initiated Routing software* ⟶ *DNS server* (one, or two or more until resolve) ⟶ *DNS resolve* * **Stage 3:** *A web Server which is part of a server environment of a computer system with the "resolved" IP address processes the server request* * **Stage 4:** *HTTP/S web Server response* (with a resolved domain) ⟶ *Server-initiated routing software* ⟶ *Client* (human or software) Regarding stage 2, I understand that **some** ISP routing software will try to lookup/resolve/translate a given domain with a given IP address "somewhere in the internet" and because that IP address can be associated with one or more DNS servers, the routing software would have to go through all DNS servers in the world until it reaches one which can "resolve" or "translate" the domain to an IP address and then the rest of the process will continue. How do World Wide Web interactions work in a general level (was my general description correct or "enough-accurate")?