Stream: implementers
Topic: Searching via POST + Percent Encoding
Weiyu Zhang (Dec 03 2021 at 04:19):
Hi all,
Quick question for the group on percent encoding and searching via POST instead of GET - the spec mentions that in searching via GET/query string parameters, percent encoded content should have the same meaning as the unencoded flavor link:
This escaping is at a different level to the % encoding that applies to all URL parameters. Standard % escaping still applies, such that these URLs have the same meaning:
GET [base]/ValueSet?url=http://acme.org/fhir/ValueSet/123,http://acme.org/fhir/ValueSet/124,125
GET [base]/ValueSet?url=http://acme.org/fhir/ValueSet/123,http://acme.org/fhir/ValueSet/124%2CValueSet/125
Does this equivalence also apply to application/x-www-form-urlencodedcontent in the body (when searching via POST)? E.g., should we accept : as a literal (even though it should be escaped based on the content type)?
Thanks in advance!
Last updated: Apr 12 2022 at 19:14 UTC
