I'm new to NGINX and can't really tell if there's a problem with it or with our app. My PHP application has a php package Device Detector that is responsible for User Agent info as well as CodeIgniter, which has a file UserAgent.php. I had an event where about 30 ppl tried accessing it. After they did the login, the message above showed up and only when we cleared NGINX cache the problem went away. We tried to replicate this error by switching GET to POST when testing the server but haven't been successful. We used loader.io to test server access and it runs fine (as do other apps on this server).Any ideas on how we could replicate it and what the problem is? Thanks
Asked
Active
Viewed 115 times
1 Answers
1
Most probably you have a badly coded application that blocks access when it is unable to detect "User-Agent" but returns the page with an error message with the normal HTTP 200 code instead of 403. As the return code doesn't indicate any errors then the error page gets cached and shown to all visitors until the cache is cleared.
AlexD
- 8,747
- 2
- 29
- 38
-
That makes sense, thanks. I know it's probably hard to tell but do you know if the problem could be with the CodeIgniter file UserAgent.php? – Cris Tecelo Dec 22 '21 at 19:18
-
Just search all your code files for the text of the error message. – AlexD Dec 22 '21 at 19:20
-
I have just found it. Thanks – Cris Tecelo Dec 22 '21 at 20:05