So by using RFC2616 protocol it can translate between string lengths so your system can handle it. "Translate" is the term I used as non tech people pissed off with the site always down may be reading and this is an accurate way to describe it without going into data path widths.

DMcG just said that by using this system to translate, it doesn't need to translate.

mmm. I think there was something about misinformation too. Clearly.

Out of interest, I mentioned iPhone 5s as this was the first 64 bit iPhone and iOS updates cannot handle anything earlier because they decided all code was to be 64 bit to avoid what DmC reckons isn't an issue "in the least." Whilst this is concerned with programming around the processor, it does show that squashing and expanding is needed. Web browsers are updating all the time with less legacy support to avoid bottlenecks.

Protocols are supposed to overcome different platform architecture limitations but they don't, never have and never will. I have Chrome on my iMac, not because its better in any way than Safari but certain propriety websites won't work in Safari. if RFC2616 did what it said on the tin, this would not be an issue.

My point stands. In 2019, even the appearance of Mudcat.org never mind the steam traction engine pulling it is not fit for the excellent purpose it serves, and the downtime clearly demonstrates this.