Comment 3 for bug 1731268

Revision history for this message
Jan Claeys (janc) wrote :

Checked with Firefox develop tools, and now I see the OOPS is in the HTTP response headers:

OOPS-3a24e5fafbbca7c7eda19766c2a02b97