JMeter does not interpret meta http-equiv="refresh" meaning we have a discrepancy in response times

[Nicola Hayward]

We have recently moved from LoadRunner to JMeter.

On one of our scripts we have noticed that There is a 4 second delay (before refresh) that is incorporated in the code.
LoadRunner picks this up and is able to handle the meta http-equiv="refresh" (hence this is why we see a representative response time). Whereas JMeter, does not interpret meta http-equiv="refresh"

Why does JMeter ignore the refresh and is there a way we can get JMeter to interpret it.

Thank you

----------------------------------------------------------------------
If you wish to view the St. James's Place email disclaimer, please use the link below.

https://www.sjp.co.uk/site-services/site-disclaimer/sjp-email-disclaimer

[Deepak Shetty]

The main reason is JMeter is not a browser(http://jmeter.apache.org/) so it
does not understand HTML specific stuff.
Hence such things need to be explicitly coded into your script

regards
deepak

Post by Nicola Hayward
We have recently moved from LoadRunner to JMeter.
On one of our scripts we have noticed that There is a 4 second delay
(before refresh) that is incorporated in the code.
LoadRunner picks this up and is able to handle the meta
http-equiv="refresh" (hence this is why we see a representative response
time). Whereas JMeter, does not interpret meta http-equiv="refresh"
Why does JMeter ignore the refresh and is there a way we can get JMeter to interpret it.
Thank you
----------------------------------------------------------------------
If you wish to view the St. James's Place email disclaimer, please use the link below.
https://www.sjp.co.uk/site-services/site-disclaimer/sjp-email-disclaimer