peterhalicky commented on PR #517:
URL:
https://github.com/apache/httpcomponents-core/pull/517#issuecomment-2724567181
> The same could be done for the fragment component.
The fragment component often contains all kinds of content. Sometimes it is
`application/x-www-form-urlencoded`, other times it looks like a path, i.e. `/`
separated path segments. Representing the fragment component as
`List<NameValuePair>` will only support the former, but not the latter.
A possible solution could be to let the client build the fragment by parts,
specifying how much encoding should be done for each part. Something like
`.appendFragment("&", URIC)` and `.appendFragment("valuewith&", RESERVED)`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
