What is the maximum length of a URL in different browsers?

Created 06.01.2009 16:14
Viewed 1.38M times
5141 votes

What is the maximum length of a URL in different browsers? Does it differ among browsers?

Is a maximum URL length part of the HTTP specification?

FWIW, for Windows users, server paths exceeding 250 characters may cause grief when building URLs, for example, see HttpContext.Current.Server.MapPath fails for long file names at forums.asp.net. bottom line: if one restriction does not get you, another one may. by gerryLowry, 02.08.2012 20:32
@gerryLowry: Windows tools already tend to have problems even compiling with long file names, so this usually isn't a concern if you only use MapPath for actual file names. One hopes that the extra-long url names are not paired with extra-long file paths, since the latter results in an unusable mess whereas the former may just be a developer abusing get requests where he should be using post requests. by Brian, 18.02.2013 12:41
From support.microsoft.com/kb/208427 "Maximum URL length is 2,083 characters in Internet Explorer" by gavenkoa, 27.02.2013 13:17
May I ask why did you need to know that? I.e. what's the use-case for having a long URL? by o0'., 08.04.2013 12:47
Related ServerFault question about Tomcat: serverfault.com/questions/56691/… by Raedwald, 12.09.2013 11:32
Related ServerFault question about Jetty: serverfault.com/questions/136249/… by Raedwald, 12.09.2013 11:33
@Lohoris: If a form uses get rather than post, then bookmarking the page reached by the filled-in form will capture the information that was entered. In some cases, that can be bad, but in other cases it can be useful. For that to work, however, the browser has to be able to handle a URL containing all the information. by supercat, 10.12.2013 22:03
@Lohoris When we write pages to generate reports we used a criteria form. It is useful on some reports to be able to email the url to someone with the criteria built in. Depending on the report we are at times forced to use post or the criteria gets truncated. Just another use case. by buzzsawddog, 06.02.2014 16:32
If your input needs to be in URL parameters, then you might want this as long as possible. Tableau allows you to embed webpages into dashboards, and make the URL dynamic based on what the user clicks on. I might want to pass a 100's of pages of text as a URL param to do some sentiment analysis and then return a result. These 100's of pages of text would change depending on which book the user clicks on. by ThomasRones, 29.09.2017 15:28
@o0'. Parameters. Especially user-defined ones. by Jacob Ford, 14.09.2019 05:13
@o0'.A good example of a long URL is when I'm asking Clickatell to send a message. I have to include the message itself in URL format (e.g. space is %20) as well as the other parameters. by Philip Kearns, 06.03.2020 09:41
Show remaining 6 comments
Answers 19

Short answer - de facto limit of 2000 characters

If you keep URLs under 2000 characters, they'll work in virtually any combination of client and server software.

If you are targeting particular browsers, see below for more details on specific limits.

Longer answer - first, the standards...

RFC 2616 (Hypertext Transfer Protocol HTTP/1.1) section 3.2.1 says

The HTTP protocol does not place any a priori limit on the length of a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15).

That RFC has been obsoleted by RFC7230 which is a refresh of the HTTP/1.1 specification. It contains similar language, but also goes on to suggest this:

Various ad hoc limitations on request-line length are found in practice. It is RECOMMENDED that all HTTP senders and recipients support, at a minimum, request-line lengths of 8000 octets.

...and the reality

That's what the standards say. For the reality, there was an article on boutell.com (link goes to Internet Archive backup) that discussed what individual browser and server implementations will support. The executive summary is:

Extremely long URLs are usually a mistake. URLs over 2,000 characters will not work in the most popular web browsers. Don't use them if you intend your site to work for the majority of Internet users.

(Note: this is a quote from an article written in 2006, but in 2015 IE's declining usage means that longer URLs do work for the majority. However, IE still has the limitation...)

Internet Explorer's limitations...

IE8's maximum URL length is 2083 chars, and it seems IE9 has a similar limit.

I've tested IE10 and the address bar will only accept 2083 chars. You can click a URL which is longer than this, but the address bar will still only show 2083 characters of this link.

There's a nice writeup on the IE Internals blog which goes into some of the background to this.

There are mixed reports IE11 supports longer URLs - see comments below. Given some people report issues, the general advice still stands.

Search engines like URLs < 2048 chars...

Be aware that the sitemaps protocol, which allows a site to inform search engines about available pages, has a limit of 2048 characters in a URL. If you intend to use sitemaps, a limit has been decided for you! (see Calin-Andrei Burloiu's answer below)

There's also some research from 2010 into the maximum URL length that search engines will crawl and index. They found the limit was 2047 chars, which appears allied to the sitemap protocol spec. However, they also found the Google SERP tool wouldn't cope with URLs longer than 1855 chars.

CDNs have limits

CDNs also impose limits on URI length, and will return a 414 Too long request when these limits are reached, for example:

(credit to timrs2998 for providing that info in the comments)

Additional browser roundup

I tested the following against an Apache 2.4 server configured with a very large LimitRequestLine and LimitRequestFieldSize.

Browser     Address bar   document.location
                          or anchor tag
Chrome          32779           >64k
Android          8192           >64k
Firefox          >64k           >64k
Safari           >64k           >64k
IE11             2047           5120
Edge 16          2047          10240

See also this answer from Matas Vaitkevicius below.

Is this information up to date?

This is a popular question, and as the original research is ~14 years old I'll try to keep it up to date: As of Sep 2020, the advice still stands. Even though IE11 may possibly accept longer URLs, the ubiquity of older IE installations plus the search engine limitations mean staying under 2000 chars is the best general policy.

06.01.2009 16:22
Note that IE11 won't bookmark URLs longer than 260 characters. I'm unsure if Edge has the same limitation. by Brian, 14.03.2016 18:05
Today IE11 cuts my URL to 2048 chars. by AntiCZ, 13.06.2016 11:04
in Chrome in 2016 I've been able to open a url with 260300 ascii chars using the osx open command from a simple script, and could confirm that all the characters were passed through to the server. The url in the browser gets truncated to 32791 characters, concludinding with ... (%E2%80%A6%E2%80%A6) by Rob Dawson, 27.09.2016 11:19
I'm noticing long URLs not work in a web app I am working on. Still debugging but I know it breaks at 4,000 character so I'm assuming Edge 38 has the same limitations as IE11's 2048? by JP DeVries, 30.09.2016 21:53
@Paul Dixon It's really nice to see people that are willing to go above and beyond in answering questions on this site. Obviously people are showing their gratitude with the current upvote count being 3734, but I wanted to say thanks! :) by drognisep, 25.09.2017 19:20
Is GET parameters included in this 2000 limit of URL? by cytsunny, 06.10.2017 09:26
@cytsunny yes they are by Paul Dixon, 06.10.2017 12:15
Is this true for modern browsers? stackoverflow.com/questions/46629900/… by Lokesh Agrawal, 09.10.2017 17:52
Is the limit inclusive of the length of the URL fragments? IOW, does this answer speak only about the part of the URL before the '#' or does it speak of the total length of the URL (inclusive of the part before the '#', the '#' and the part after the '#')? by kaartic, 01.01.2018 14:26
As of Jan 2018, IE 11 shrinks URLs, replaced by window.location to the 4095 characters. by Roman Bekkiev, 18.01.2018 10:15
IE11: max-length for anchor: 5120 bytes, max-length for address-bar: 2047, max-length for copying to address-bar: 2083 by Stefan Steiger, 21.03.2018 13:56
is a space (%20) considered as one character or 3 characters? by Jun711, 28.05.2018 17:28
Popular answer indeed... Google figures this post is the authority, based on the snippet provided before search results when searching for "maximum url length". :) by ashleedawg, 08.09.2018 08:25
Googler Hohn Mueller said: "As far as I know, there's no theoretical length limit, but we recommend keeping URLs shorter than 2000 characters to keep things manageable." here productforums.google.com/forum/#!topic/webmasters/dPxWiO-cRn‌​M/… by Ivan Kutas, 27.11.2018 14:44
It appears that IE11 and MS Edge 42 (Win10) both allow large urls if you redirect to them.... You can't edit them in the browser (if you type in the address bar, it'll limit you), but you can redirect to large urls (at least 3.5k) by Brad Parks, 23.01.2019 16:08
Also, if you want to test an url that's 4032 chars in total length via redirect, just go tinyurl.com/ezbigurl11 and it'll redirect you to httpbin.org, with a dump of the request that was just made to that server. by Brad Parks, 24.01.2019 14:58
I'm noticing that on Chrome, mailto: links longer than 2048 characters fail. On Firefox I seem to be able to go up to just over 32K. by Charles T, 17.06.2019 15:13
Still valid as of September 2019. Just hit the IE/Edge limit on a particularly spicy Splunk query URL. by hiergiltdiestfu, 17.09.2019 20:54
This is a really good answer and I'd like to add to this. Even if you forget about Internet Explorer and sitemaps, CDNs also impose limits on URI length. Most CDNs suppor the minimum required request-line lengths of 8000 octets and return 414 Too long request when reached. Fastly 8kb, CloudFront: 8,192 bytes, Cloudflare 32KB by timrs2998, 02.01.2020 20:59
Thanks @timrs2998, I've added those link into the body of the answer by Paul Dixon, 06.01.2020 18:33
My old mobile provider used some MITM hackjob cache/gateway thing that prevened me from accessing certain websites, because the URL got too long. It was clearly not even close to 2000 charcters and worked fine over other internet connections. So there's that as well... by PixelSupreme, 07.02.2020 10:26
Mentioning any version of IE in 2020 update is ... strange. by Petr Nagy, 19.02.2020 15:41
What about HTTP/2 ? Does the upcoming HTTP/3 add something new to this subject? by Stephan, 25.05.2020 11:09
@PaulDixon As of Jan 2019 Microsoft switched their rendering engine to Blink. Could this warrant another limitation check? Edge is now at version 83 by hitautodestruct, 25.05.2020 11:36
Did you come back a few days ago to update the answer? Awesome stuff by Marvin, 02.09.2020 10:15
@Marvin yes! I'm astonished this is now 11 years old - I think it's time to review all the information presented, but I believe the core advice still stands. by Paul Dixon, 03.09.2020 10:39
Kudos to still updating it at Sept 2020! by corroded, 17.09.2020 02:46
@PetrNagy Sadly, in corporate environments, IE11 is still quite frequent. by jcaron, 26.11.2020 16:07
Show remaining 23 comments

The longest URLs I came across are data URLs

Example image URL from Google image results (11747 characters)

18.07.2012 23:12
He's talking about the fact that a base64 encoded jpeg is technically a URL, because it's specified as data:*. While he's correct in stating that it is a valid URL, I don't think that's what the question was asking. by Fitblip, 08.01.2013 08:24
... or just paste it in your address bar. by Gras Double, 27.06.2013 01:49
Because a data URL contains the protocol "data:", and the identifier, it's everything you need to LOCATE that "file" (even if the "Filesystem" is the space of all possible files). It is therefore a URL, which is also a URI. (But definitely not "not a URL") by MickLH, 24.05.2014 18:19
@DoubleGras Google Chrome for Mac does not allow me to paste a URL that long into my address bar by Max Nanasy, 27.05.2014 23:34
Thanks for the info. I've just tested it successfully on Firefox and Chrome, Windows. So… it simply depends ;) by Gras Double, 28.05.2014 12:09
Hmm. This could be considered an answer, but it seems fairly clear that the OP was asking about URLs using the http or https scheme... by SamB, 15.01.2015 00:20
The Chrome extension "Webpage screenshot" previews the screenshot as a data URI. A page 32708 pixels high (1263 wide) became a PNG 8,749,309 bytes (8.34 MiB) in length. In base64, that's 11,665,748 characters. Add in the data:image/png;base64,, and you get a 11,665,770 character long data URI. by Cole Johnson, 03.03.2015 04:05
I cannot even paste this in current Chrome. by The Onin, 14.12.2016 00:37
A few firefox versions ago I generated a 2MB URI image. You could display it on a page, but pasting it to the address field\opening in a new tab, resulted in a crash every time I tried. by jahu, 06.06.2017 08:40
@Nino Škopac It's working in Chrome Version 76.0.3809.87 (Official Build) (64-bit). Pasting it into the location bar displays a cartoon of the Google home page. by George, 31.07.2019 03:51
Applause for the "Is this information up to date?" section! I have never seen this before, but this is crucial in fast-moving tech. by Brian Risk, 06.05.2020 15:16
2021.02: The image url in this answer does work in Chrome 88 on Mac by Larry K, 25.02.2021 06:42
Is that.... Sergey and Larry? by rgshenoy, 06.04.2021 09:07
Show remaining 8 comments

I wrote this test that keeps on adding 'a' to parameter until the browser fails

C# part:

public ActionResult ParamTest(string x)
    ViewBag.TestLength = 0;
    if (!string.IsNullOrEmpty(x))
                       new[] {Request.UserAgent, x.Length.ToString()});
        ViewBag.TestLength = x.Length + 1;

    return View();


<script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>

<script type="text/javascript">
    $(function() {
        var text = "a";
        for (var i = 0; i < parseInt(@ViewBag.TestLength)-1; i++) {
            text += "a";

        document.location.href = "http://localhost:50766/Home/ParamTest?x=" + text;


On Chrome I got:

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36

It then blew up with:

HTTP Error 404.15 - Not Found The request filtering module is configured to deny a request where the query string is too long.

Same on Internet Explorer 8 and Firefox

Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0


I went easy mode and added additional limits to IISExpress applicationhost.config and web.config setting maxQueryStringLength="32768".

Chrome failed with message 'Bad Request - Request Too Long

HTTP Error 400. The size of the request headers is too long.

after 7744 characters.

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36



    <add header="Content-type" sizeLimit="32768" />

which didn't help at all. I finally decided to use fiddler to remove the referrer from header.

static function OnBeforeRequest(oSession: Session) {
    if (oSession.url.Contains("localhost:50766")) {

Which did nicely.

Chrome: got to 15613 characters. (I guess it's a 16K limit for IIS)

And it failed again with:

<BODY><h2>Bad Request - Request Too Long</h2>
<hr><p>HTTP Error 400. The size of the request headers is too long.</p>

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36


Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0

Internet Explorer 8 failed with iexplore.exe crashing.

Enter image description here

After 2505

Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)

Android Emulator

Mozilla/5.0 (Linux; Android 5.1; Android SDK built for x86 Build/LKY45) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/ Mobile Safari/537.36

Internet Explorer 11

Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)

Internet Explorer 10

Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)

Internet Explorer 9

Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
06.07.2015 16:14
So, in effect, my assumption of 512 chars is largely wrong ^_^ Thanks for the test. I will never care about the query param length anymore.. by Gogol, 17.09.2015 07:19
This should be the accepted answer... the first one doesn't actually provide hard limits for each browser which is what the questions asks for. by GrayedFox, 08.04.2016 09:23
Might be worth looking into Safari too. Safari is the only browser that does not support client-generated downloads. The workarounds are: a) open a BLOB URI (a short, temporary URI that points to an in-memory Blob) in a new window, b) open a base-64 encoded data URI in a new window (may be very long, but supports mime typing). Details here: github.com/eligrey/FileSaver.js/issues/12 by Mat Gessel, 28.09.2016 18:16
@Vaitkevicius do u know if a space(%20) is counted as one character or 3? by Jun711, 28.05.2018 17:26
@Jun depends where... press F12 and paste following into the console console.log("%20".length +" "+decodeURI("%20").length) this should explain it by Matas Vaitkevicius, 29.05.2018 02:06

WWW FAQs: What is the maximum length of a URL? has its own answer based on empirical testing and research. The short answer is that going over 2048 characters makes Internet Explorer unhappy and thus this is the limit you should use. See the page for a long answer.

06.01.2009 16:18

There is really no universal maximum URL length. The max length is determined only by what the client browser chooses to support, which varies widely. The 2,083 limit is only present in Internet Explorer (all versions up to 7.0). The max length in Firefox and Safari seems to be unlimited, although instability occurs with URLs reaching around 65,000 characters. Opera seems to have no max URL length whatsoever, and doesn't suffer instability at extremely long lengths.

05.08.2010 10:17
If the instability is around 65k it is probably right there near 65535 (2^16 - 1). Maybe they loop through chars using short i? Just a thought. I wonder what URL they tested for 65k+ o_o;; by Garet Claborn, 18.03.2011 11:46
This answers is maybe the one that should be accepted, as it provides the concrete answers: 2k for IE, 65k for Safari/Firefox, "more" for Opera. by eis, 15.04.2013 06:20
I'm curious. Is the 65k URL a data scheme URI or really a URL in the classic sense? by SaAtomic, 14.09.2017 10:50

On Apple platforms (iOS/macOS/tvOS/watchOS), the limit may be a 2 GB long URL scheme, as seen by this comment in the source code of Swift:

// Make sure the URL string isn't too long.
// We're limiting it to 2GB for backwards compatibility with 32-bit executables using NS/CFURL
if ( (urlStringLength > 0) && (urlStringLength <= INT_MAX) )

On iOS, I've tested and confirmed that even a 300+ MB long URL is accepted. You can try such a long URL like this in Objective-C:

NSString *path = [@"a:" stringByPaddingToLength:314572800 withString:@"a" startingAtIndex:0];
NSString *js = [NSString stringWithFormat:@"window.location.href = \"%@\";", path];
[self.webView stringByEvaluatingJavaScriptFromString:js];

And catch if it succeed with:

- (BOOL)webView:(UIWebView *)webView shouldStartLoadWithRequest:(NSURLRequest *)request navigationType:(UIWebViewNavigationType)navigationType
    NSLog(@"length: %@", @(request.URL.absoluteString.length));
    return YES;
27.06.2016 06:49
You sir deserve a +1 just for the effort of trying a 300MB URL by Дамян Станчев, 10.11.2016 12:57
iOS isn't a browser in and of itself. Was this in Safari for iOS? by Randall, 07.08.2017 14:21
@Randall schemes are handled by the OS and then dispatched to the app that can open them. So all apps on iOS, including Safari, can handle long URI. by Cœur, 07.08.2017 14:35
Thanks for the clarification. Presumably, though, this doesn't prevent an arbitrary app (say, eg, a Tor-powered browser) from introducing its own length restriction, correct? by Randall, 07.08.2017 15:13

The URI RFC (of which URLs are a subset) doesn't define a maximum length, however, it does recommend that the hostname part of the URI (if applicable) not exceed 255 characters in length:

URI producers should use names that conform to the DNS syntax, even when use of DNS is not immediately apparent, and should limit these names to no more than 255 characters in length.

As noted in other posts though, some browsers have a practical limitation on the length of a URL.

06.01.2009 16:20

The HTTP 1.1 specification says:

URIs in HTTP can be represented in absolute form or relative to some
known base URI [11], depending upon the context of their use. The two
forms are differentiated by the fact that absolute URIs always begin
with a scheme name followed by a colon. For definitive information on
URL syntax and semantics, see "Uniform Resource Identifiers (URI): Generic Syntax and Semantics," RFC 2396 [42] (which replaces RFCs 1738 [4] and RFC 1808 [11]). This specification adopts the definitions of "URI-reference", "absoluteURI", "relativeURI", "port",
"host","abs_path", "rel_path", and "authority" from that

The HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs.*
A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15).

Note: Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations might not properly support these lengths.

As mentioned by @Brian, the HTTP clients (e.g. browsers) may have their own limits, and HTTP servers will have different limits.

06.01.2009 16:26

Microsoft Support says "Maximum URL length is 2,083 characters in Internet Explorer".

IE has problems with URLs longer than that. Firefox seems to work fine with >4k chars.

26.05.2010 16:18

In URL as UI Jakob Nielsen recommends:

the social interface to the Web relies on email when users want to recommend Web pages to each other, and email is the second-most common way users get to new sites (search engines being the most common): make sure that all URLs on your site are less than 78 characters long so that they will not wrap across a line feed.

This is not the maximum but I'd consider this a practical maximum if you want your URL to be shared.

08.01.2013 00:38
I wonder where "78" comes from? Maybe that original 1999 article was written under the assumption that people are reading their email in 80x24 terminal windows? Still, good advice! by Jon Schneider, 28.01.2015 21:23
Well. IBM punch cards were also 80 columns. With two characters taken up by a carriage return and a line feed you get 78. by Paul Morgan, 28.01.2015 21:39
Haha. :-) I was actually considering referencing 1981-era 80x25 CGA monitors in my comment, but you reached even further back! ...I wasn't around for the punch card era, but were they 80 bytes across, or only 80 bits? by Jon Schneider, 28.01.2015 21:43
Not exactly a byte (8 bits). It encoded one character in each column. by Paul Morgan, 29.01.2015 08:44
@JonSchneider - 78 is quite specific, and may relate to readability of text (from a usability perspective given Nielsen's background), which is best between 50-60, and a maximum of 75. by Jay Rainey, 16.03.2016 13:06

Sitemaps protocol, which is a way for webmasters to inform search engines about pages on their sites (also used by Google in Webmaster Tools), supports URLs with less than 2048 characters. So if you are planning to use this feature for Search Engine Optimization, take this into account.

14.08.2011 12:50
This is a little confusing. Sitemap protocols "supports URLs with less than 2048 characters." I imagined a site like example.com would work. I think this question is more about the maximum? by HoldOffHunger, 17.08.2018 17:21

ASP.NET 2 and SQL Server reporting services 2005 have a limit of 2028. I found this out the hard way, where my dynamic URL generator would not pass over some parameters to a report beyond that point. This was under Internet Explorer 8.

23.07.2013 23:17

Why is the Internet Explorer limit only 2K while IIS has a limit of 16K? I don't think it makes sense.

So I want to start an experiment about Ajax request URL size limits.

I have set my Tomcat HTTP connector's maxHttpHeaderSize="1048576". And prepared a very long URL.

Then I send a request with the long URL like the following:

var url="/ajax/url-length.jsp";

jQuery reports done. Tomcat reports the URL requested is 1048015 bytes. It was tested with Chrome 50 and Internet Explorer 11.

So web browsers won't truncate or limit your URL intentionally when sending Ajax requests.

04.05.2016 12:23
The variation between Internet Explorer and IIS makes sense when you consider that not all requests to a web server are done via a browser. by TroySteven, 12.01.2018 16:39

Limit request line directive sets the maximum length of a URL. By default, it is set to 8190, which gives you a lot of room. However other servers and some browses, limit the length more.

Because all parameters are passed on the URL line, items that were in password of hidden fields will also be displayed in the URL of course. Neither mobile should be used for real security measures and should be considered cosmetic security at best.

28.08.2013 10:11

It seems that Chrome at least has raised this limit. I pasted 20,000 characters into the bookmarklet and it took it.

14.12.2014 19:56

I have experience with SharePoint 2007, 2010 and there is a limit of the length URL you can create from the server side in this case SharePoint, so it depends mostly on, 1) the client (browser, version, and OS) and 2) the server technology, IIS, Apache, etc.

15.01.2015 02:54
Because SharePoint exposes web URLs as file paths, it runs into a separate limitation: the Windows file path length limit of 260 characters (or 248 characters when using an API). For more details about this limit, check out the "Maximum Path Length Limitation" section here: msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx by Thriggle, 20.05.2015 18:48

According to the HTTP spec, there is no limit to a URL's length. Keep your URLs under 2048 characters; this will ensure the URLs work in all clients & server configurations. Also, search engines like URLs to remain under approximately 2000 characters.

21.09.2019 07:09
Just remove or comment the following lines

public void ConfigureServices(IServiceCollection services) { /Identity/ services.AddDbContext(options => options.UseSqlServer(Configuration["ConnectionStrings:IdentityConnection"])); services.AddIdentity<AppUser, IdentityRole>().AddEntityFrameworkStores().AddDefaultTokenProviders(); /End/

        /*Identity Login Url */
        services.ConfigureApplicationCookie(opts => opts.LoginPath = "/Login");

        //services.AddMvc(config =>
        //    var policy = new AuthorizationPolicyBuilder()
        //                    .RequireAuthenticatedUser()
        //                    .Build();
        //    config.Filters.Add(new AuthorizeFilter(policy));
03.02.2021 11:57

Check this answer: It has described all the browsers in details.


05.05.2021 17:52