[MGNLRESTCL-166] Rest client app cannot handle parameter values that contain a "=" Created: 25/Nov/20 Updated: 25/Nov/20 |
|
| Status: | Open |
| Project: | REST Client |
| Component/s: | None |
| Affects Version/s: | 1.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Will Scheidegger | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
When you need to pass in a parameter value which contains a "=" character (e.g. the Base64 encoded "Authorization" value), you're out of luck because the parsing of the parameter value will fail. This boils down to RestClientAppPresenter.parseParameters(), which simply splits the line in segments by "=". |