[Webkit-unassigned] [Bug 186039] Prevent websites from talking to loopback interface (127.0.0.1, localhost)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 30 12:35:46 PDT 2018


https://bugs.webkit.org/show_bug.cgi?id=186039

--- Comment #10 from ctclements at gmail.com ---
(In reply to Brent Fulgham from comment #9) 
> I doubt IT departments are excited about you running invalidated server
> software on their corporate machines. Installing a certificate is a very low
> bar in comparison.

So far, no issues there.  Is there a way that self-signing a certificate and installing it makes make my server software any more or less validated?

Irregardless of my specific use case, the point is that 3/4 relevant (in my industry) browsers are following the spec.  There is a reason we have web specifications.  Not following the specification ends up in odd cases like this where we either have to write more code to accomadate the one browser that doesn't follow the other 3, or simply tell customers we don't support the browser.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180530/47a49a3a/attachment.html>


More information about the webkit-unassigned mailing list