[Webkit-unassigned] [Bug 80616] [WebSocket] implement strict URL validator

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Mar 9 09:49:42 PST 2012


--- Comment #2 from Takashi Toyoshima <toyoshim at chromium.org>  2012-03-09 09:49:42 PST ---
I guess Kent-san think WebSocket specific validator is overkill.
So, how about introducing strict mode in KURL.
Of course, it doesn't mean that I modify KURL interfaces.

Currently, chromium port of KURL doesn't apply strict check for usability and compatibility.
On the other hand, the implementation knows the scheme of provided URL.
My idea is introducing strict validation mode only for ws:// and wss:// schemes implicitly
inside KURL implementation (of chromium port).

WebSocket schemes are newly launched and don't have to keep backward compatibility now.
If we apply lazy validation for WebSocke, we overlooks non-conforming sites.
It could cause the chance of future compatibility issue.

But, basically, I agreed that WebSocket specific another validator is overkill as Kent-san said.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list