Header value with equals sign is incorrectly written

[GoogleCodeExporter]

What steps will reproduce the problem?
1. In the header pane, enter a header whose value includes an equals sign, like 
"Authorization: GoogleLogin auth=test"

What is the expected output? What do you see instead?
The header should be written in the request with the equals sign. Instead, the 
equals sign gets translated into a colon, like "Authorization: GoogleLogin 
auth:test". See screenshot.

What version of the product are you using? On what operating system?
1.0.3 Windows 7 32

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 16 Nov 2011 at 6:14

Attachments:

• Capture.PNG

[GoogleCodeExporter]

Thanks benhirashima for raising issues. They are quite valid and I'll include 
them in next release.

I believe it still passes correct header to request though it shows = replaced 
by : . Anyway I'll double check and will remove this discrepancy .

Original comment by a1yadu on 16 Nov 2011 at 6:42

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Issue 14 has been merged into this issue.

Original comment by a1yadu on 19 Mar 2012 at 6:16

[GoogleCodeExporter]

The problem here is the function RCUtil.getMapFromStr(), which splits the 
headers on "=". Within the Authentication header there are many "=" character, 
also at the end of the value, which are truncated by the used String.splt() 
function.

Original comment by [email protected] on 14 Aug 2012 at 11:34

Attachments:

• rcutil-patch.txt

[GoogleCodeExporter]

Original comment by a1yadu on 18 Jul 2013 at 7:34

• Changed state: Started

[GoogleCodeExporter]

Issue 19 has been merged into this issue.

Original comment by a1yadu on 18 Jul 2013 at 8:00

[GoogleCodeExporter]

I have confirmed that if you add an = sign in a header value, it does not pass 
the = properly.

In my case I am trying to send a Basic Auth header, and the base64 encoding has 
an = sign at the end.  Through packet traces, I can confirm the = sign is NOT 
passed to the server.

Original comment by [email protected] on 1 Dec 2013 at 1:24

[GoogleCodeExporter]

I'm not sure how this could be considered a "low priority" defect.  This 
basically prevents the tool from being useful at all to anyone testing an 
endpoint with authentication enabled.  Thats... pretty critical.

Original comment by [email protected] on 5 Mar 2015 at 12:01