TECHNOLOGY

Guidelines on how to ruin bandwidth, battery vitality, and annoy sysadmins

Okay, let’s focus on something different than feed readers for a 2d.
How about solely broken net browsers? Yeah, those.

This. That is a thing. Depend the broken:

ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 26 -0700] "GET /w/css/significant.css HTTP/1.1" 200 1651 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/feed.png HTTP/1.1" 200 689 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed/ HTTP/1.1" 200 8052 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 
ip - - [28/Jun/2024: 14: 44: 27 -0700] "GET /w/2024/05/27/feed//favicon.ico HTTP/1.1" 404 20 

First up, why within the hell pause it be crucial to inquire the identical hyperlink 12 instances?
No, scratch that, 15 instances, since it does 3 extra after getting the css
and feed icon.

Then it goes for the favicon, and what clown made up our minds that the coolest way
to inquire “/favicon.ico” is to prepend the inaccurate course to it? This
cursed thing that Microsoft foisted upon us encourage within the 90s is meant
to be at the pinnacle stage. Or no longer it’s miles no longer half of particular particular person directories. That
could possibly presumably presumably be dreary.

And but, this thing decides to beat the shit out of the net server whereas
attempting to derive it.

I earlier skool to shock ultimate what could possibly presumably very neatly be this dreary. The user-brokers on
these abominable requests are no longer particularly in fact helpful. Nonetheless, then within the future, I
received lucky and seen that the significant inquire of the narrate has one very
attention-grabbing little ingredient in it (whereas the others pause no longer):

FxiOS/127.1

FxiOS. That is, Firefox for iOS. That by itself used to be ample to derive me
having a find, and oh, ogle what I found out.

Put a query to of spamming when visiting a set up of dwelling

Put a query to of unsolicited mail for favicon and apple-contact icons on iOS 16 + Firefox 105

Put a query to of Flooding when opening app

favicon.ico is in / , it appears to be for favicon.ico in each and each directory aside from / .

Firefox on iPhone makes a flood of requests for icons

Enticing. So, at the same time as you shatter up the utilization of this garbage, know that you’re potentially
leaving a bolt of badness to your wake.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button