Comment 2 for bug 1619675

This definitely seems to be a server bug but I'm not sure why.

Could you also provide the headers from when you don't encounter the error? I suspect that might provide some insight.