Scott Eade wrote:
I have two questions pertaining to the results of recording a session using
the HTTP Proxy Server.

1. If I record a HTTP session using the proxy, each request is created with
a child HTTP Header Manager object.  Should these be retained in the test
script for playback or can they be discarded?  I can see that the header
manager would be useful if I wanted to manually manipulate the headers (say
if the application behaviour depended upon the presence of certain headers),
but what if my application doesn't care?  I would also imagine that the keep
alive flag on the http request, as well as the host, referrer, etc. would
all be sent automatically by JMeter in the absence of the HTTP Header
Manager - is this correct?
You can remove all the HeaderManager objects and your tests will still work. The HeaderManager is important only if your applications uses header fields (e.g. UserAgent) to generate different responses.

2. When a session is recorded, individual HTTP Requests are created for any
images that are encountered in the session.  I seem to recall the
documentation indicating that these should be discarded in favour of using
the "Retrieve All Images and Java Applets (HTML files only)" option on HTTP
Requests for actual web pages.  I see two problems here:
A. Using the "Retrieve All" option does not seem to retrieve all of the
images that were recorded during the proxy session.
B. When the "Retrieve All" option is used, the same images appear to be
retrieved over and over (e.g. images in the site navigation) rather than
mimicking the cache behaviour of the browser (i.e. retrieve on the first
occurrence, use the cache on subsequent occurrences - as is recorded by the
proxy).
It appears that the "Retrieve All" option is not doing all that it should,
is this correct?
It is possible to filter the image requests by using the include/exclude patterns of the proxy settings. The "Retrieve All" option is not working for me either. To get reasonable numbers out of the tests JMeter should behave like a browser and, as you said, should simulate a browser's cache behaviour. I have plans to implement this but it will take some time because I'm working on GUI stuff at the moment.


Oliver

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to