In the header for a request to an API, I have removed the header 'Accept-Encoding' because it's generating a 401 error. However, when I check the user path validity, it's still showing in the details of the request and I cant see why?
Any ideas?
It is automatically added by NeoLoad while replaying a request. But are you sure that it's responsible of your 401 errors?
This kind of error is related to an authentication issue. Do you need to authenticate against your server and if yes what type of authentication?
It is responsible for the 401 error because when I make the same request in postman with Accept-Encoding' it generates a 401 error but when it's removed, it results in the correct 200 response code.
How do I prevent NeoLoad from automatically adding it while replaying the request?
I am also getting same error. I am using 2 versions of Neoload 5.3.1 and 6.5.1.
The accept encoding header automatically gets added in the 5.3 version but works perfectly fine for 6.1 version. Is updating the latest Neoload version the only option to resolve this issue?
In 6.5.1, you can choose the values of Accept-Encoding in the browser configuration of the population. For the Check User Path, the browser configuration is in the Advanced dialog.
Alexis answered
Abhiram answered
Christopher answered
Nouredine answered
Christopher posted a new question
