I have simple scenario: I want to manage a website's response time for posting data typed into a form. There are 4 steps:
1. GET login.html 2. POST credentials.html 3. POST data.html 4. GET logout.html
These steps are quite easy to setup, however, on authentication (step 2) the server responds with a HTTP redirect (HTTP status code 302). This is a very common behavior in modern web applications, but PRTG regards this as an error; skipping the transaction.
I believe this handling is wrong since HTTP 3xx Redirection codes aren't errors.
Is there a way to accomplish this scenario or am I doing any mistakes?