These two URLs result in different strings generated!
WHATWG is written by idiots.
Browsers are doing their own thing btw!
file://localhost/path/to/somethere
file://127.0.0.1/path/to/somewhere
WHATWG is written by idiots.
Browsers are doing their own thing btw!
😁1
WHATWG mindset:
-
-
-
file::::::: totally valid URL-
http:: hold on, that's not valid at all!😁2🔥1🤣1
This is a valid WHATWG URL with a hidden "Hello World" binary message encoded within:
-
-
-
/ is 1-
\ is 0https:/\\//\\////\\\\//\\/\\/\\\\/\\\\///\\\\/\\\\///\\\\/\\\\\\\\//\\//////\\/\\/\\\\\\/\\\\/\\\\\\\\/\\\\\\//\\//\\\\/\\\\///\\\\//\\//example.com👍1
I don't know whom is to blame, but this is a valid URL:
fILe://C|\\//\////\\\\/\/\/\\\/\Why on earth tabs and newlines are just IGNORED in URLs and spaces are invalid characters?
WHO hurt you WHATWG?
WHO hurt you WHATWG?
Web++: A C++ Web Framework
2625 failed tests out of 4986 for the WHATWG tests I generated for my URI Parser Is that bad?
Down to only 2621 failed tests, yaaay 😅😬
😁2👍1
Merged upstream changes of my liburing C++ified fork.
Still some UBs remain (liburing itself heavily relies on UB).
Header-Only liburing fork
Still some UBs remain (liburing itself heavily relies on UB).
Header-Only liburing fork
👍1
Media is too big
VIEW IN TELEGRAM
The White House: use Memory Safe languages
Youtube Link | white house press release
Full Report (A PATH TOWARD SECURE AND MEASURABLE SOFTWARE)
Youtube Link | white house press release
Full Report (A PATH TOWARD SECURE AND MEASURABLE SOFTWARE)
😁1
Back_to_the_building_blocks_a_path_toward_secure_and_measurable.pdf
591.5 KB
White house full technical report about memory safety in languages among other things.
WHATWG mindset:
Valid URLs:
Invalid URLs:
Valid URLs:
file:
any-random-scheme:
Invalid URLs:
http:
https:
ws:
wss:
ftp:
😁2