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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 30 12:07:16 PDT 2018


ctclements at gmail.com changed:

           What    |Removed                     |Added
                 CC|                            |ctclements at gmail.com

--- Comment #8 from ctclements at gmail.com ---
I'm adding another request to please follow the web standards on this.  Especially now that Edge has fixed this and will be pushing it out soon.  Chrome, Firefox, and Edge all follow the web standard.  As a developer with a legitimate use of web technology, it is beyond frustrating to see you go against the web standard.

This leaves me with two options...

1: Go the self-signed certificate route.  This results in my installer asking to install a certificate and for the user to trust it.  This then results in them getting their IT security teams involved, multiple phone calls going back and forth on why it is okay to install the certificate, and other headaches.  

2: Write my code to handle things differently on OSX/Windows.  Users on Chrome/Firefox/Edge on Windows will not need the certificate.  Users on Safari will.  

Neither of these options is acceptable.  Both of these options are completely avoidable by following web standards.  At this point I don't know what else to do other than strongly suggest that our customers don't use WebKit based browsers.

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/6205f665/attachment.html>

More information about the webkit-unassigned mailing list