Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465)

I have a log viewer app that is behind a vpn that I am now not able to access because of this.
I think the premise of 

> Usage of the http://user:pass@host/ pattern has declined significantly
in the last few years; 

is wrong. Just because you're not getting it in your analytics doesn't mean it's not happening. I personally just don't allow you to collect these analytics, and I'd wager a bet there are many more like me. 

How about instead of a breaking change, and pushing your opinions on others, you just issue a warning about it when it happens, and allow the warning to be dismissed?

This is a feature people use, and you just took it away without just cause IMHO. 

I think the most frustrating part is you page:
https://www.chromestatus.com/feature/5669008342777856

states: 
> Consensus & Standardization
  Firefox:  No public signals
  Edge: No public signals
  Safari: No public signals
  Web Developers:  No signals

I'm a Web Developer, and part of a company of 100+ others, we want this feature back without a launch flag. Hope that's a clear enough signal for ya.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/465#issuecomment-313678141