Mastodon Feed
neatnik@social.lol ("Neatnik") wrote:
@NfNitLoop Thanks for the report! I got egemi up and running and it helped me discover an unrelated bug in the Splashdown code, and I just got that fixed. But for the PHP bug, I think the issue here is egemi isn't handling the meta tied to the status 10 payload correctly. What's happening on the server end when /hello.php is requested is this exact response:
10 What's your name?\r\n
Position 6 in the string that's sent with with the 10 payload is in fact byte 32 (as reported in the egemi error), which is a space character (the space between "What's" and "your"). Normally spaces aren't OK in the meta here, since that's where a MIME type is usually expected, but status 10/11 responses are an exception. The spec defines those payloads as free-form text prompts meant to be displayed to a user, not a MIME type as you'd normally get with a 2X status.
So this could be a bug in the mime parser, or in the underlying egemi code (since technically the browser shouldn't be treating what comes after 1X codes as a MIME type, so it shouldn't really be trying to parse that, but rather displaying it as an input prompt per the spec). Let me know if I can offer any other info or set up any test pages to help with this further!