5 ms·
The state of proliferating sites that won't let you access them because you're not using an "approved" browser with JS and cookies enabled, and hiding behind th
by userbinator 4y ago
The state of proliferating sites that won't let you access them because you're not using an "approved" browser with JS and cookies enabled, and hiding behind the "security" excuse to do so. Ironic that I can't even read an article about HTTP in 2022 because of that racket.
Thanks, Cloudflare.
- zdragnar 4y agoIt isn't your security they're concerned about, it is the server's- it is preventing DDoS attacks. If you want to blame someone, blame the people who poisoned the well for everyone else.
- maxbond 4y agoWe can walk & chew gum here, spammers and DDoSers are poisoning the well for sure, but Cloudflare is responsible for externalities of their service.
- deleted 4y ago[deleted]
- zdragnar 4y agoServer hosts want protection from DDoS. They hire a bouncer (I e. Cloudflare) to keep the hordes at bay. The bouncer asks for some way to distinguish your suspicious looking request from that of the start of a DDoS attack. How is this an "externality" of cloudflare's service? If anything, it is an "externality" of the server hosts.
- maxbond 4y agoDoes it even matter? Blame is irrelevant, I find responsibility to be a more interesting thing to discuss in virtually all circumstances. The DDoSers and spammers should cut it out (but unfortunately we can't really count on them for anything), Cloudflare should make more of an effort to preserve accessibility, and their customers should care about it too & make it clear to Cloudflare that it's a priority to them. But if we take a step back it's clear that Cloudflare is the entity here that can have the biggest impact. Spammers and customers are diffuse, Cloudflare isn't. How much of the blame they deserve, I don't really care, but theres a problem, they're in the best position to act, so they have a responsibility to. In my opinion, that's the best mindset for solving problems.
- zdragnar 4y ago> Blame is irrelevant, I find responsibility to be a more interesting thing to discuss This is, to me, a bizarre notion. You're imposing some sort of moral edict upon cloudflare for providing an opt-in service to web hosts. > they're in the best position to act They have, and they decided that certain traffic requires additional consideration to distinguish from bad actors. Your refusal to cooperate is entirely on you. Just because you don't like their solution doesn't mean that there is a better one. If you have better ideas, I'm sure they're all ears, as less intrusive is generally cheaper to implement.
- userbinator 4y agoit is preventing DDoS attacks. Is it? Those who want to DDoS will always find a way, and meanwhile users with slightly odd hardware/software are being locked out. Admittedly the latter is a minority, but one of the key tenets of the Internet and what made it so successful was interoperability. This is, in some ways, even worse than (but somewhat of a following effect of) the effective browser monopoly. Calling it "security" when it's really about "availability" is another deceptive misdirection, because the former is something that can more easily persuade the sheeple. I don't really like to go to extremes, but fingerprinting clients and deciding access based on such should really be regarded as a moral equivalent to racial profiling.
- zdragnar 4y agoProfiling happens all the time for entirely legitimate reasons in the real world. Racial profiling is immoral not because it is profiling; it is immoral because it is based on immutable characteristics which have no intrinsic bearing on the purpose of the profile. To tie this back to the topic at hand, you're complaining that a service has decided your traffic resembles known patterns from bad actors, and is asking you to go through an extra step to access the content. Are there better options? Maybe, but it's utterly asinine to compare what cloudflare is doing to racial profiling.
- jayd16 4y ago> Those who want to DDoS will always find a way How do you figure? You don't think far more DDoS events would occur if it was easier and more effective?
- cortesoft 4y ago> Those who want to DDoS will always find a way Not really. We are actually pretty good these days at stopping DDOS attacks.
- mysterydip 4y agoNot sure how accurate this is, but currently shows 150+ DDoS attacks going on globally: https://www.netscout.com/ddos-attack-map https://www.netscout.com/ddos-attack-map
- deleted 4y ago[deleted]
- worldofmatthew 4y agoDDOS attacks that exist because Cloudflare knowly protects booter websites which feeds the DDDOS economy with money to make DDOS botnets profitable?
- mnot 4y agoThe IETF is working on a solution to this, and Cloudlare is actively contributing and implementing; see https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/ https://blog.cloudflare.com/eliminating-captchas-on-iphones-...
- dceddia 4y agoThis plan looks even worse for privacy, and seems to rely on authenticating the unique device itself. > Know your user is coming from an authentic device and signed application, verified by the device vendor directly. If they manage to get wide adoption of something like this it seems like a very bad day for privacy, and a joyous day for advertisers, anyone who wants to prevent web scraping, Google and/or anyone who might want to make it hard to crawl the entire web…
- mnot 4y agoRead a bit more; that’s not how the cryptography works. They’re blinded tokens.
- dceddia 4y agoI read further, and it sounds like they've designed it with privacy in mind. That's nice. I'm still having a hard time seeing how this doesn't eventually lead to a completely locked-down internet, where users can only use approved browsers and devices. They have a list of steps for how a request would be made, where steps 2 and 3 are: > 2. Safari supports PATs, so it will make an API call to Apple’s Attester, asking them to attest. > 3. The Apple attester will check various device components, confirm they are valid, and then make an API call to the Cloudflare Issuer (since Cloudflare acting as an Origin chooses to use the Cloudflare Issuer). In a theoretical future world where 99% of site operators have set this up for protection, and 99% of users are using approved browsers, how would one do something like... Create a competitor to Google? You'd need to crawl the web for that. Would you imagine Apple or Cloudflare would gladly let your device request millions of tokens per hour? Or would that be throttled or disallowed entirely? Use curl (or telnet, or [any other HTTP client]) to grab a page? Use yt-dlp to download a YouTube video? Scrape a bunch of data for an AI project? See this article from the front page where someone scraped a bunch of car listings from KBB and trained a model to estimate car prices and found some interesting results. https://blog.aqnichol.com/2022/12/31/large-scale-vehicle-classification/ https://blog.aqnichol.com/2022/12/31/large-scale-vehicle-cla... - would something like that be permitted under a system like this? Or might you need to own/rent an army of authorized devices with authorized browsers to do that experiment?
- ddon 4y agoMay be this link will work for you? https://archive.ph/1gcnQ https://archive.ph/1gcnQ
- userbinator 4y agoThanks for trying, but unfortunately archive.ph is also behind Cloudflare.
- anenefan 4y agoFunny enough I can actually view their article. Despite that I can visit websites where admins that set permissions not overly tough, I still run into enough blocks due to cloudflare that I'm considering investing time (ok for the last few years I've been really really lazy, I'm happy enough to copy and paste so I can manually write a nasty comment ) so that for each "bad load" the web site can be added to my disallow list. It might only save the smallest amount of wasted bandwidth but I guess it all adds up.
- deleted 4y ago[deleted]
- 1vuio0pswjnm7 4y agoThe "new" HTTP is clearly targeted at the "approved browser". For example, this alleged "head-of-line blocking problem" that HTTP/2 purportedly "solves" was never a problem of HTTP outside of a specific program, the graphical web browser, the type of client that tries to pull resources from different domains for a single website. Not all programs that use HTTP need to do that. For instance I have been using HTTP/1.1 pipelining outside the browser for fast, reliable information retrieval for close to 20 years. It has always been supported by HTTP servers and it works great with the simple clients I use. I still rely on HTTP/1.1 pipelining today, on a daily basis. Never had a problem. There are uses for pipelining besides the ones envisioned by "tech" companies, web developers and their advertiser customers.
- mnot 4y agoIf early hints breaks your proxy, it’s likely your proxy doesn’t handle 1xx status codes correctly. Could you tell me which proxy it is (privately if you think it necessary)? I’d like to chase the bug with them.
- raggi 4y agoThe big problem with pipelining in http 1.x is that a response can break the pipeline part way through and there is no way to know what the server processed. A response night for example, mid pipeline be connection:close and that’s that, did any subsequent request get processed? Who knows.
- 1vuio0pswjnm7 4y agoHTTP/2 seems to be designed for (graphical, interactive) webpages. The maintainer of a popular webserver has suggested HTTP/2 is slower than HTTP/1.1 for file download. https://stackoverflow.com/questions/44019565/http-2-file-download https://stackoverflow.com/questions/44019565/http-2-file-dow... As I stated, I use HTTP/1.1 pipelining every day. I use it for a variety of information retrieval tasks, even retrieving bulk DNS data. To give an arbitrary example, sometimes I will download a website's sitemaps. This usually involves downloading a cascade of XML files. For example, there might be a main XML file called "index.xml". This file then lists hundreds more sitemap XML files, e.g., archive-2002-1.xml, archive-2002-2.xml, containing every content URL on the website beginning with some prior year all the way up to the present day. Using a real world example, index.xml contains 246 URLs. Using HTTP/1.1 pipelining I can retrieve all of them into a single file using a single TCP connection. Then I retrieve batches of the URLs contained in that file, again over a single TCP connection. Many websites allow thousands of HTTP requests HTTP/1.1-pipelined over a TCP single connection, but I usually keep the batch size at around 500-1000 max. Of course I want the responses in the same order as the requests. The process looks something like this ftp -4o 1 https://[domainname]/sitemaps/index.xml yy030 < 1|(ka;nc0) > 2 yy030 < 2|wc -l 1337855 1337855 is the number of URLs for [domainname]. Content URLs, not Javascript, CSS or other garbage. yy030 is a C program that filters URLs from standard input ka is a shell alias that sets an environment variable that is read by the yy025 program to indicate an HTTP header, in this case the "Connection:" header set to "keep-alive" not "close" (ka- sets it back to close) nc0 is a one line shell script yy025|nc -vv h1b 80|yy045 yy025 is a C program that accepts URLs, e.g., dozens to hundreds to thousands of URLs, on stdin and outputs customised HTTP h1b is a HOSTS file entry containg the address of a localhost-bound forward TLS proxy yy045 is a C program that removes chunked transfer encoding from standard input To verify the download, I can look at the HTTP headers in file "2". I can also look at the log from the TLS proxy. I have it set configured to log all HTTP requests and responses. Is this a job for HTTP/2. It does not seem like it. This type of pipelining using only a single TCP connection is not possible using curl or libcurl. Nor is it possible using nghttp. Look around the web and one will see people opening up dozens, maybe hundreds of TCP connections and running jobs in parallel, trying to improve speed, and often getting banned. As with the comment from the Jetty maintainer, I suspect using HTTP/2 would actually be slower for this type of transfer. It is overkill. IMHO, HTTP, i.e., in the general sense, is not just for requesting webpages and resources for webpages. I find HTTP/1.1 to be very useful. It is certainly not just for requesting webpages full of JS, CSS, images and the like. That is only one way I might use it. Perhaps HTTP/2 is the better choice for webpages. TBH, if using a "modern" graphical browser, I would be inclined to let it use HTTP/2. Most of the time I am not using a graphical browser.
- svnpenn 4y agoYep. Just try to cURL the page, and you get 403 Forbidden. That is completely unacceptable.