Hey! Good to see progress being made towards finalisation. Hopefully the spec will be final soon! > The first is that the specification is now explicit about what to do in the event that a request including a query component receives a 3x redirect status code in response: the redirect URL should be used as is, and the client should not apply the original request's query to the redirect URL. If you are the author of a client which *does* modify redirect URLs in this way, you need to change this behaviour in order to be spec compliant. Could you please elaborate on what "apply the original request's query to the redirect URL" means? I'm not sure what this forbids. > The second is that the specification now explicitly forbids the use of Unicode byte order marks (BOMs) in either Gemini requests or Gemini response headers. If your client or server includes a BOM in these places, you should stop doing that. There will be a future update dealing with the use of BOMs in Gemini response bodies as well, but the changes I just pushed affect only response headers. This would only apply to text/gemini, right? So not any arbitrary Unicode document (possibly under UTF-16 or UCS encodings)? But welcome change anyway. BOMs suck! Cheers, almaember
---
Previous in thread (1 of 5): 🗣️ Solderpunk (solderpunk (a) posteo.net)
Next in thread (3 of 5): 🗣️ Justin Abrahms (justin (a) abrah.ms)