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 2017/11/14 10:03:53 UTC
[Bug 61753] New: Jmeter proxy server encodes the request sent to
server during recording
https://bz.apache.org/bugzilla/show_bug.cgi?id=61753
Bug ID: 61753
Summary: Jmeter proxy server encodes the request sent to server
during recording
Product: JMeter
Version: 3.3
Hardware: PC
Status: NEW
Severity: blocker
Priority: P2
Component: HTTP
Assignee: issues@jmeter.apache.org
Reporter: dinesh.k3@tcs.com
Target Milestone: ---
Steps to reproduce:
1. Recorded an simple HTTP applicaiton using JMeter 3.3
2. Application sends a bunch of API calls to the server during a transaction.
3. These API calls has JSON request captured by JMeter in parameter name
section.
4. JMeter encodes the double quotes, space using URL Encoded - UTF8.
5. But the server doesnt understand the request and throws HTTP 500 error.
Response shows error message as 'Invalid input'
6. Recorded the same user actions using chrome developer tool, LoadRunner etc.,
the data is sent as plain JSON text without encoding
7. Problem arises only when JMeter proxy comes in.
Is there any way to turn off/deactivate the encoding while recording in
JMeter.?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61753] Jmeter proxy server encodes the request sent to server
during recording
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61753
--- Comment #2 from Dinesh Kumar <di...@tcs.com> ---
Created attachment 35531
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35531&action=edit
Reqeust
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61753] Jmeter proxy server encodes the request sent to server
during recording
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61753
Dinesh Kumar <di...@tcs.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #4 from Dinesh Kumar <di...@tcs.com> ---
Please find patched screenshots showing the request and response error.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61753] Jmeter proxy server encodes the request sent to server
during recording
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61753
--- Comment #3 from Dinesh Kumar <di...@tcs.com> ---
Created attachment 35532
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35532&action=edit
response
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61753] Jmeter proxy server encodes the request sent to server
during recording
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61753
Felix Schumacher <fe...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #5 from Felix Schumacher <fe...@internetallee.de> ---
(In reply to Dinesh Kumar from comment #4)
> Please find patched screenshots showing the request and response error.
Could you try to give us text examples instead of those garbled screenshots?
I can't guess, what you are trying to show, from those screenshots.
Just type the headers you are seeing with and without using JMeter as a proxy.
Same for the response. It doesn't have to be your production data. You can use
simple values, that are close enough.
For example:
Request (without proxy):
Content-Type: foo
Request (with proxy):
Content-Type: foo-bar
Response (without proxy):
['abc': 23]
Response (with proxy):
['def': 42]
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61753] Jmeter proxy server encodes the request sent to server
during recording
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61753
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEEDINFO |RESOLVED
--- Comment #6 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
No feedback, closing.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61753] Jmeter proxy server encodes the request sent to server
during recording
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61753
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|blocker |normal
OS| |All
CC| |p.mouawad@ubik-ingenierie.c
| |om
Status|NEW |NEEDINFO
--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
(In reply to Dinesh Kumar from comment #0)
> Steps to reproduce:
>
> 1. Recorded an simple HTTP applicaiton using JMeter 3.3
> 2. Application sends a bunch of API calls to the server during a transaction.
> 3. These API calls has JSON request captured by JMeter in parameter name
> section.
> 4. JMeter encodes the double quotes, space using URL Encoded - UTF8.
> 5. But the server doesnt understand the request and throws HTTP 500 error.
> Response shows error message as 'Invalid input'
> 6. Recorded the same user actions using chrome developer tool, LoadRunner
> etc., the data is sent as plain JSON text without encoding
> 7. Problem arises only when JMeter proxy comes in.
>
> Is there any way to turn off/deactivate the encoding while recording in
> JMeter.?
Hello,
We would need more details to work on this issue:
- Can you provide the test plan you use for recording ?
- Can you provide a capture of the failing request ? and examples of requests ?
- An HAR file might be interesting if you're using Chrome
--
You are receiving this mail because:
You are the assignee for the bug.