[book] Old version of the book gets mixed up with new version -> style on <code> elements makes them impossible to read

[jmillikin]

Google sent me to this link for the libAFL tutorial: https://aflplus.plus/libafl-book/baby_fuzzer.html

Which currently looks like this on my machine (Chrome 145.0.7632.160, macOS):

[...]

At first I thought this was a humorous stylistic choice for the introductory paragraph, but it's present through the entire page. A bit of investigation shows that there's two versions of the book kinda mashed together under https://aflplus.plus/libafl-book/. The newer version (https://aflplus.plus/libafl-book/baby_fuzzer/baby_fuzzer.html) looks correct.

I'm not sure exactly what the build pipeline looks like for that site, but it might be good to clean up older HTML before generating the new HTML. Or set up some redirects for traffic inbound from search engines.

[atharva-potdar]

Google sent me to this link for the libAFL tutorial: https://aflplus.plus/libafl-book/baby_fuzzer.html

This link renders correctly right now. Has the issue been fixed?

[jmillikin]

Still renders with the same broken version for me (Chrome 150.0.7871.127).

Screenshot of https://aflplus.plus/libafl-book/baby_fuzzer.html (the broken version that Google likes):

Screenshot of https://aflplus.plus/libafl-book/baby_fuzzer/baby_fuzzer.html (the correct version? found via other links):

[atharva-potdar]

Oh yeah you're right, on the "broken" link you can't change the theme (first thing I noticed, maybe more stuff is broken too). I didn't notice it at first because my browser defaulted to dark mode, where the broken link looked correct.
Not sure why the old file would still be there honestly, shouldn't it have been deleted when they moved it?

[jmillikin]

My assumption is that there's some build step like "copy new files to the server with cp -r build_output /var/www/" and it just never deletes files.

My first instinct was also that old files (not present in the new build) should be deleted, but for SEO reasons it would probably be better to intentionally write them out with a stub redirect. Then the copy would overwrite them.