You can't use a 102 http status code in Azure

Chris Child | 2019-06-21 | 1 min read

You can't use a 102 status code because Azure will always wait for a follow up code. In my code I changed it to a 202 Accepted instead.

If you try and use a 102 in Azure, you will eventually get a 502 response, which states that the server received an invalid response while acting as a proxy or gateway. Which translates to, I received a 102 but not a final status code from you code.

A 102 should only ever be used to say that the call is still in progress ans must always be followed up with a final status code, be that a 200 or 202 like I changed mine to.

Comments

Related Posts

nextsycl is a Rust + SYCL runtime for Intel Arc that runs a 63 GB MoE on one 32 GB Arc Pro B70 — the experts that don't fit live in pinned host RAM, the PLE table is streamed from disk, and MTP drafts double the single stream. What it took to get 1,200 tok/s prompt read and ~78 tok/s decode, including the prompt-cache bug that made every agent turn pay a full re-read.