Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

They are not, but you can encode them, if you encode whitespace characters, you included whitespace in a URL.

One of the requirement of URLs is that it needs to be transmissible over paper or aural media, so arbitrary octets and the unused portion of ASCII are not legal either.



Don't forget about pigeon packets. https://www.rfc-editor.org/rfc/rfc2549


Seems to be RFC 1149, btw, (what you linked is about Pigeon QoS.)

Somwhere after DNS IP and SMTP, but still before HTTP(1.0).




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: