Is there any possibility that the name of a header and the name of a query parameter (on the URL or in the body) could collide? - N-Infra #195

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Very High
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • OperationOutcome
    • Hide
      • Add an example of location referring to a search parameter which does not need quotes (not using a modifier).
      • Clarify the language so it is clear this section talks about the fhirpath paths used in the "expression" element, not the deprecated "location" element.
      • Add a note saying that if the convention in the spec is used (where headers are capitalized and search parameters start with a lower case), no collisions can occur, and the implementers are encouraged to stick to the same convention.
      Show
      Add an example of location referring to a search parameter which does not need quotes (not using a modifier). Clarify the language so it is clear this section talks about the fhirpath paths used in the "expression" element, not the deprecated "location" element. Add a note saying that if the convention in the spec is used (where headers are capitalized and search parameters start with a lower case), no collisions can occur, and the implementers are encouraged to stick to the same convention.
    • Grahame Grieve/Josh Mandel: 7-0-0
    • Non-substantive
    • STU3

      Comment:

      Is there any possibility that the name of a header and the name of a query parameter (on the URL or in the body) could collide?

      Summary:

      Is there any possibility that the name of a header and the name of a query parameter (on the URL or in the body) could collide?

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: