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/03/02 08:47:55 UTC
[Bug 60800] New: Content type charset in Request Headers
https://bz.apache.org/bugzilla/show_bug.cgi?id=60800
Bug ID: 60800
Summary: Content type charset in Request Headers
Product: JMeter
Version: 3.1
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: HTTP
Assignee: issues@jmeter.apache.org
Reporter: dr.hemachandar@gmail.com
Target Milestone: ---
Created attachment 34791
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34791&action=edit
Jmeter - v2.9
I am trying to upload a file to a dbserver. As per my request format everything
is working fine. But there is an issue in HTTP Request Headers. I have added
common http headers through the request. But Content-Type is added additionally
through the request header.
The actual problem arises when reading the boundary value. JMeter additionally
share charset in the content-type which is not actually needed for request
headers.
This was faced in version 3.1. But in Jmeter 2.9 there is no charset shared in
the request headers and it is processing successfully.
Please let me know how to disable the charset in content type for HTTP request
headers.
Attaching the screenshot of Request headers for v3.1 and v2.9.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 60800] Content type charset in Request Headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60800
--- Comment #5 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Hello @Hemachandar,
Can you test nightly build tomorrow and report wether this bug is fixed for you
?
- http://jmeter.apache.org/nightly.html
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 60800] Content type charset in Request Headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60800
--- Comment #1 from Hemachandar <dr...@gmail.com> ---
Created attachment 34792
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34792&action=edit
Jmeter - v3.1
Jmeter - v3.1
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 60800] Content type charset in Request Headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60800
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |p.mouawad@ubik-ingenierie.c
| |om
Resolution|--- |DUPLICATE
Status|NEEDINFO |RESOLVED
--- Comment #4 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
*** This bug has been marked as a duplicate of bug 61384 ***
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 60800] Content type charset in Request Headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60800
--- Comment #3 from Hemachandar <dr...@gmail.com> ---
Created attachment 34793
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34793&action=edit
http request
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 60800] Content type charset in Request Headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60800
UbikLoadPack support <su...@ubikloadpack.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #2 from UbikLoadPack support <su...@ubikloadpack.com> ---
Hello,
Can you show how your HttpRequest is configured ?
Possibly attaching a short JMX plan instead of screenshot ?
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 60800] Content type charset in Request Headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60800
Hemachandar <dr...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
CC| |dr.hemachandar@gmail.com
--
You are receiving this mail because:
You are the assignee for the bug.