You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2018/09/24 10:00:48 UTC
[Bug 62756] New: Jmeter, does not interpret meta
http-equiv="refresh"
https://bz.apache.org/bugzilla/show_bug.cgi?id=62756
Bug ID: 62756
Summary: Jmeter, does not interpret meta http-equiv="refresh"
Product: JMeter
Version: 4.0
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: abhishek.sanauria@sjp.co.uk
Target Milestone: JMETER_5.1
There is a 4 second delay (before refresh) that is incorporated in the code,
LR 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"
How we can handle that in jmeter?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 62756] Jmeter, does not interpret meta http-equiv="refresh"
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62756
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
CC| |p.mouawad@ubik-ingenierie.c
| |om
OS| |All
--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
There is no issue here.
Use recorder , this will be catched and recorder.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 62756] Jmeter, does not interpret meta http-equiv="refresh"
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62756
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|JMETER_5.1 |---
--
You are receiving this mail because:
You are the assignee for the bug.