Timeline for which component handle php's GET parameters in a URL
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2017 at 10:57 | history | edited | L Martin | CC BY-SA 3.0 |
changing answer
|
| Feb 8, 2017 at 10:27 | comment | added | L Martin | Then use a rewrite module in Apache - to remove the query strings? | |
| Feb 8, 2017 at 10:19 | comment | added | CoffeDeveloper | Ops in hurry mis-readed the amswer. We don't want to block GET (otherwise we would block all pages ^^). We want to get rid of the logic that translate url parameters. We don't need them, and if possible we want to get rid of modules Handling that translation (still too early to customize the webserver build, we just want to work from installation configuration, for now). | |
| Feb 8, 2017 at 10:10 | comment | added | MrWhite |
<Limit GET>deny from all</Limit> - will simply block all GET requests, ie. all regular HTTP requests! The $_GET PHP superglobal refers only to the query string, which is what the OP appears to be referring to. (?)
|
|
| Feb 8, 2017 at 10:06 | comment | added | CoffeDeveloper |
Thanks, I think there's also some logic to be disabled in PHP, the part that translates ?name=Hannes to $_GET["name"]
|
|
| Feb 8, 2017 at 10:06 | history | edited | MrWhite | CC BY-SA 3.0 |
Code formatting
|
| Feb 8, 2017 at 10:04 | history | answered | L Martin | CC BY-SA 3.0 |