Reputation
439
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 11 33
Impact
~57k people reached

  • 0 posts edited
  • 1 helpful flag
  • 95 votes cast
Jan
8
awarded  Autobiographer
Dec
3
awarded  Notable Question
Nov
7
awarded  Popular Question
Oct
2
awarded  Popular Question
Sep
17
accepted Rewriting nginx's try_files
Sep
17
comment Rewriting nginx's try_files
Yep. Restarted server and second example began to work, all except for the $_GET-based routing. Anything passed after / results in the index.php loading front page with URI arguments stripped out (GET /projects => GET /)
Sep
17
comment Rewriting nginx's try_files
Tried the second example as well. Same issue there
Sep
17
comment Rewriting nginx's try_files
Hmm. In your first example, index.php will load, but any static files or URI requests such as /page1/item will return the index.php
Sep
17
comment Rewriting nginx's try_files
@Luke Updated my question with the complete config. Thank you!
Sep
17
revised Rewriting nginx's try_files
added 375 characters in body
Sep
17
comment Rewriting nginx's try_files
No change. $_GET probably works as I can access /index.php?action=projects&item=1 but both /projects & /projects/1 still equals to 404 as intended in the application
Sep
17
comment Rewriting nginx's try_files
Index.php works nicely, but anything that should be rewritten ends up in 404's
Sep
17
comment Rewriting nginx's try_files
404 is thrown with File not found. if I use either URI /page or /page/id
Sep
17
asked Rewriting nginx's try_files
Jul
3
awarded  Popular Question
Jun
14
awarded  Nice Question
Jun
8
awarded  Constituent
Jun
8
awarded  Caucus
Jun
5
awarded  Self-Learner
Apr
27
awarded  Popular Question