Support optional CRC to detect corrupted URLs

[MikeRich88]

Corrupted URLs seem to hang the browser or load a blank page in my testing.

An optional CRC could be added to the beginning of the hash. (The end would make no sense. I assume that the largest source of corruption would be truncated URLs)

CRC16 would probably be adequate while still being really short.

This would of course provide no authentication, just a detection for a corrupted or truncated URL.

[alcor]

Which browser are you seeing corruption in? Edge? If so truncation should be detected now.

[MikeRich88]

No paticular browser, just a hypothetical truncation.

If truncation is detected now then that would take care of the main problem.

[alcor]

I may consider a content length value to detect this.