Disable caching for XHR pre-flight requests

Fixed, flighted Issue #8819146

Details

Author
Michael P.
Created
Sep 9, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Fixed in build #
15002
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

When making XML requests with URLs longer then 2083 characters Edge returns this error:

XMLHttpRequest: Network Error 0x800700005, Access is denied.

This is probably caused by this restriction in WinINET.h where 2048 + 32 + 3 = 2,083.

#define INTERNET_MAX_PATH_LENGTH 2048
#define INTERNET_MAX_SCHEME_LENGTH 32 // longest protocol name length
#define INTERNET_MAX_URL_LENGTH (INTERNET_MAX_SCHEME_LENGTH
+ sizeof(“://”)
+ INTERNET_MAX_PATH_LENGTH)

https://blogs.msdn.microsoft.com/ieinternals/2014/08/13/url-length-limits/

All non-MS browsers don’t have these limitations as they properly implement RFC 2616 which does NOT specify a limit.

Upping the limit to 8192 would provide enough “headroom” for our current application needs.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rajat J.”

      Changed Title from “Edge does not support URLs longer then 2083 characters” to “Edge does not support URLs longer than 2083 characters”

    • +1000 on this. An accessible favicon creator, exporter web app I’ve submitted to 10kApart relies heavily on URLs up to around 3500 characters in length handle export
      https://github.com/jpdevries/makeanico/
      https://makeanico.azurewebsites.net

    • Microsoft Edge Team

      Changed Title from “Edge does not support URLs longer than 2083 characters” to “Disable caching for XHR pre-flight requests”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Fixed, flighted”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Insider Preview build.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in