TinyPEN may be having some trouble with this based on the same issue in RERUM (it struggles with bad and missing Content-Type headers).
Any request with an improper or missing Content-Type header gets an unexpected 500 from TinyPEN.
Load Test Evidence (Run 4, Phase 8 — Fuzzing)
From k6 Phase 8e (header manipulation):
Sending a request with duplicate/multi-value Content-Type headers to TinyPEN returned 500. No stack trace was leaked.
Expected behavior: return 400 (bad request) or simply use the first Content-Type value and proceed.
TinyPEN communicates with RERUM, and RERUM had trouble with Content-Type headers as well. The work to solve this issue goes along with the fix in RERUM. See CenterForDigitalHumanities/rerum_server_nodejs#255
TinyPEN may be having some trouble with this based on the same issue in RERUM (it struggles with bad and missing Content-Type headers).
Any request with an improper or missing Content-Type header gets an unexpected 500 from TinyPEN.
Load Test Evidence (Run 4, Phase 8 — Fuzzing)
From k6 Phase 8e (header manipulation):
Sending a request with duplicate/multi-value
Content-Typeheaders to TinyPEN returned 500. No stack trace was leaked.Expected behavior: return 400 (bad request) or simply use the first Content-Type value and proceed.
TinyPEN communicates with RERUM, and RERUM had trouble with Content-Type headers as well. The work to solve this issue goes along with the fix in RERUM. See CenterForDigitalHumanities/rerum_server_nodejs#255