Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Vind hier onze Servicedesk om een verzoek in te dienen m.b.t. onze producten en diensten! Klik hier om toegang aan te vragen of voor andere BITS/Jira gerelateerde vragen en/of opmerkingen.

PDF/A - HTTP status codes in scenario 1.3

Description

Based on https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_IG#Handling_errors a search with a syntactically incorrect parameter should lead to an HTTP 400 error. However, the automatic assert in scenario 1.3 of PDF/A checks if a code from 400,402,403,404,405,406,407,408,409,410,411,412,413,414,415,416,417,418,421,422,423,424,426,428,429,431,451,500,501,502,503,504,505,506,507,508,510,511 is present. This should be changed to only include 400 (compare with for instance scenario 1.5).

Moreover scenario 1.3 and 1.5 should be made more consistent.

Verduidelijking van Impact

Low; an automatic assert that checks if the correct HTTP status code is used is changed based on the underlying documentation.

Proposed solution (NL)

  • Change the automatic assert related to the HTTP status code in scenario 1.3 such that it only passes if code 400 is used.

  • Make scenario 1.3 and 1.5 more consistent.

Proposed solution (EN)

None

Release notes (NL)

De automatische assert gerelateerd aan de HTTP-code in scenario 1.3 is aangepast zodat deze alleen slaagt wanneer code 400 wordt gebruikt. Verder zijn scenario 1.3 en 1.5 meer met elkaar in lijn gebracht.

Release notes (EN)

The automatic assert related to the HTTP status code in scenario 1.3 has been changed so that it only passes if code 400 is used. Moreover scenario 1.3 and 1.5 have been made more consistent.

100% Done

Activity

Resolved
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Classification

Informatiestandaard onderdelen

Kwalificatie- en testmaterialen

Information standard

PDF/A 3.x

Fix versions

Priority

Better Excel Exporter

Created July 21, 2022 at 5:50 AM
Updated January 12, 2024 at 12:54 PM
Resolved August 30, 2022 at 3:13 PM