News for hackers. Stuff that matters.

A comment on Browsers barely care what HTTP status code your web pages are served with. Parent comment

Re:Browsers barely care what HTTP status code your web pages... by yonatan8070 on Friday August 11, 2023 @06:21AM (#37087030)
Yet Windows still frequently shows Error "0x0000F001" without elaborating at all
[ Parent | on HN ]
Re:Browsers barely care what HTTP status code your web pages... by Hamuko on Friday August 11, 2023 @06:39AM (#37087145)
Something happened

Something happened

[ Parent | on HN ]
Re:Browsers barely care what HTTP status code your web pages... by ElectricalUnion on Friday August 11, 2023 @11:52AM (#37090103)
Those are usually structured HRESULT values, Win32 error codes, and NTSTATUS values.

So in a way, they are already "elaborating" the type of error - as well as a single 32-bit integer in C can "elaborate" over an error, that is, not a lot.

For all their faults dotnet and java make it really easy to not mangle up the stack trace.

[ Parent | on HN ]
Re:Browsers barely care what HTTP status code your web pages... by nullindividual on Friday August 11, 2023 @12:43PM (#37090747)
You want err.exe [0].

[0] https://www.microsoft.com/download/details.aspx?id=100432

[ Parent | on HN ]