Menu
▾
▴
#2 Distinction between multiple requests
When recording a session, numerous GET requests for
pages as well as images are issued. You quickly get
lost in all those requests.
OpenSTA (http://opensta.org) makes a distinction
between PRIMARY and SECONDARY requests, which makes the
resulting script a lot more readable. I believe the
distinction is based on the different "Accept:" Header
for requests issued to load a page and parts (images)
of that page.
It'd be nice to have this in Solex too.
Olaf
Logged In: YES
user_id=555234
That is the purpose of the current "Filter HTTP Requests"
and "Filter HTTP Headers" features, isn't it?
It is actually more powerful that a basic distinction
between so-called Primary and Secondary requests since you
can precisely adjust what you want to retain in your script
based on any URL suffix (strip the images that way for
instance) and HTTP headers (Accept: or others).
Cheers,
Olivier.
Logged In: YES
user_id=45582
No, I believe both concepts are good, but in different
contexts: Filtering helps, but you have to filter .gif,
.jpg, .swf, .png etc if your site uses them. You can disable
them and have a better overview to your script, because the
yellow arrows in front of the filtered requests now are white.
Better yet would be to "invisibilize" the filtered requests,
or, to make them a sublevel entry in the treeview. This of
course would mean that you have to associate to a "primary"
request, where you can add them as a child node.
Having the distinction between primary and secondary
requests automatically sends all gifs, jpgs, swfs etc one
level deeper down the hierarchy. I believe everybody
developing and testing a webapp is not too interested in all
25 images contained in a page, but more on the few pages
hidden between the image requests. Still in playback the
images are still interesting, because they simulate "real
users" load on the webserver, if you execute hundreds of
concurrent users.
Olaf
Logged In: YES
user_id=754129
Might it be of help to just be able to add comments to
the single requests?
That way it would be easier to organise and structure
the session file.
Alex