Check modern Windows URL length limitations |
||
Issue descriptionIn chrome/browser/platform_util_win.cc, OpenExternalOnFileThread(), soon to be renamed OpenExternalOnWorkerThread(), limits URLs to 2048 characters, based on limitations in pre-Vista Windows. Maybe it's time re-evaluate this limitation, since Chromium requires Windows 7 or newer now.
,
Nov 16 2017
We probably shouldn't change this unless there's some overwhelming argument for doing so. I had a look at this a few years back and just now confirmed that Windows' ShellExecute still limits AppProtocols to 2083 characters. https://blogs.msdn.microsoft.com/ieinternals/2014/08/13/url-length-limits/ Application Protocols Application Protocols are subject to even weirder limits. On Windows 10 (build 14393), for instance, if you directly pass a 4k Application Protocol URL to ShellExecute in native code, the URL is silently truncated at the 2083 character mark. In Internet Explorer 11, attempting to launch an Application Protocol URL longer than 507 characters fails with an exception: Error message "data area was too small" In Chrome, if you attempt to an Application Protocol URL over 2046 characters, you’ll see the regular Security Prompt, but clicking its “Launch Application” button does nothing.
,
Nov 19
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by grt@chromium.org
, Jun 3 2017