Skip to main content

Timeline for Understanding of HTTP GET request

Current License: CC BY-SA 4.0

8 events
when toggle format what by license comment
Feb 25, 2023 at 15:02 comment added Tom @mentallurg I specifically wrote that this is most likely the case.
Feb 25, 2023 at 11:36 comment added mentallurg @Tom: The it is obvious that the usage of .php in URL assumes that the server is configured to pass such requests to a PHP engine. Otherwise you are inconsistent.
Feb 25, 2023 at 9:45 comment added Tom @mentallurg obvious example domain is obvious
Feb 25, 2023 at 1:48 comment added wizzwizz4 @mentallurg If we're nitpicking that much, then it says webapp.thm, not webapp.thm. – so it doesn't matter whether there's a thm TLD, since this isn't a fully-qualified domain name, and it can be resolved locally. (We can nitpick further still, and question why any assumptions are being made about the configuration of the DNS root. There are already relatively-popular alternative DNS roots out there, so that's not even unresonable.)
Feb 24, 2023 at 23:13 comment added mentallurg @Tom: Formally, you are absolutely right. But if you like nitpicking so much, then why don't you say that the question makes no sense at all, because there is no such TLD as thm, thus the website webapp.thm does not exist and the request cannot be sent anywhere and it makes no sense to ask what the server will do?
Feb 24, 2023 at 22:46 history edited Criticizing Israel not allowed CC BY-SA 4.0
added 48 characters in body
Feb 24, 2023 at 11:07 comment added Tom This is the only correct answer. The part after the domain is passed to the webserver and that decides what to do with it. Everything else is assumptions based on conventions. Most likely, it'll execute get.php and pass in the rest as a parameter, but due to rewrite rules and other server stuff, that isn't guaranteed to be the case.
Feb 22, 2023 at 18:45 history answered Criticizing Israel not allowed CC BY-SA 4.0