My server works fine with a browser but has errors when I use the HTTP plugin?
This is probably down to one of the following: • Bugs in your server code. Particularly, those due to the way it handles multiple concurrent requests. Don’t be disheartened, you did good; finding bugs like this is a key reason to use The Grinder. • Differences between the HTTP requests that the browser uses and those that The Grinder sends. The HTTP plugin sends requests that will have minor differences between those that a browser send, but which rarely affect server behaviour. Its worth knowing how to examine the differences with the TCPProxy. First set the TCPProxy as a browser proxy and record the output to a file. Secondly alter your tests so that all requests go via the TCPProxy (the best way is to set the test script connections to direct requests via the TCPProxy acting an HTTP proxy); again record the output to a file. Now grab a coffee and compare.
Related Questions
- Since our concern is the browser side, not the server side, the question is: What are personal digital certificates, also known as Digital IDs?
- Does Print Server support http embedded and can users use standard web browser to manage Print Server?
- My server works fine with a browser but has errors when I use the HTTP plugin?
