Request-URI Too Large

Hi, I am working on a project that involves exporting excel spreadsheets to a JSP script for special charting and as a result the URLs can be very long like: http://preview.tinyurl.com/p9vykm (full URL shown in tinyurl preview). As a result of this, servers typically complain about the URL being too large to process even though browsers like Firefox will happily accept such long URLs. So obviously a alternative method of passing this data to my JSP script must be saught, and it must be a manageable method able to be performed with VBA which is unfortunately being used to interact between the excel spreadsheet and this script. My thought was base64 encrypting the parameters, passing that to the JSP script and then having the JSP script decrypt the encrypted parameters and process them. Is that possible and if so how? If not, how would you think it best to approach this issue? Thanks!

Yes, it's true. Servers are allowed to put a limit on the length of a URL when it's used for a GET request. There's nothing you can do about that. However if you use a POST request, then the parameters are passed differently and they don't count as part of the length. I have no idea whether VBA can be made to use POST instead of GET.
I don't see why Base64 encoding would help, since it's guaranteed to increase the size of the string by one third. You need something which reduces the size of the string.

Similar Messages

How to get rid of Yahoo's "Sorry, Request-URI Too Large"

Whenever I "search" for anything, some message pops up from Yahoo preventing the search.

This issue can be caused by corrupted cookies.
Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
* Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove Cookies" from sites causing problems:
* Tools > Options > Privacy > Cookies: "Show Cookies"
If clearing the cookies doesn't help then it is possible that the file <i>cookies.sqlite</i> that stores the cookies is corrupted.
Rename (or delete) <b>cookies.sqlite</b> (cookies.sqlite.old) and delete <b>cookies.sqlite-journal</b> and <b>cookies.txt</b>, if they exist, in the Firefox Profile Folder in case the file cookies.sqlite got corrupted.
* http://kb.mozillazine.org/Profile_folder_-_Firefox

(413) Request Entity too large intermittent error

I have page in a SharePoint 2013 website which is viewed over https. The page has several input fields including two file upload controls. I am trying to upload a sample picture less than 1MB for each of the controls.
I am calling a BizTalk WCF service on Submit. Sometimes, when I try to submit I get ‘413 Request Entity Too Large'. This error happens intermittently though because if I try submitting the same data a number of times, it fails sometimes and works other times.
The binding settings for the service are set in code (not in Web.Config) as shown below ...
var binding = RetrieveBindingSetting();
var endpoint = RetrieveEndPointAddress(“enpointAddress”);
var proxy = new (binding, endpoint);
proxy.Create(request);
public BasicHttpBinding RetrieveBindingSetting()
var binding = new BasicHttpBinding
MaxBufferPoolSize = 2147483647,
MaxBufferSize = 2147483647,
MaxReceivedMessageSize = 2147483647,
MessageEncoding = WSMessageEncoding.Text,
ReaderQuotas = new System.Xml.XmlDictionaryReaderQuotas
MaxDepth = 2000000,
MaxStringContentLength = 2147483647,
MaxArrayLength = 2147483647,
MaxBytesPerRead = 2147483647,
MaxNameTableCharCount = 2147483647
Security =
Mode = BasicHttpSecurityMode.Transport,
Transport = { ClientCredentialType = HttpClientCredentialType.Certificate }
return binding;
I have also set the uploadReadAheadSize in applicationHost.config file on IIS as by running the command below, as suggested here ...
appcmd.exe set config "sharepoint" -section:system.webserver/serverruntime /uploadreadaheadsize:204800 /commit:apphost
Nothing I do seems to fix this issue so I was wondering if anyone had any ideas?
Thanks

Sounds like it's not a SharePoint problem, does the page work correctly if you don't call the BizTalk WCF service? And what happens if a console app is calling the WCF service independently of SharePoint, does it fail then as well? In both cases, it would
limit the troubleshooting scope to the WCF service, which gets you a step further.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Requested buffer too large - but data is already in memory

Hello all,
I am writing a program that generates sound and then uses the Java Sound API to play it back over the speakers. Until recently, using clips have not led to any problems. On two computers I can play the sound without a hitch. However, on the newest computer (and also with the largest specs and especially more RAM), I am getting an error while trying to play back the sound. The exception that is thrown is:
javax.sound.sampled.LineUnavailableException: Failed to allocate clip data: Requested buffer too large.
I find this odd because the buffer already exists in memory: I don't have to read in a .wav file or anything because I am creating the audio during the course of my program's execution (this is also why I use Clips instead of streaming - the values are saved as doubles during the calculations and then converted into a byte array, which is the buffer that is used in the clip.open() method call). It has no problems allocating the double array, the byte array, or populating the byte array. It is only thrown during clip.open() call. I also find it strange that it would work on two other computers, both of which have less RAM (it runs fine on a machine with 512MB and 2GB of RAM, both XP 32-bit). The only difference is that the computer with the issue is running Windows 7 (the RTM build), 64-bit with 6GB of RAM. I am running it through Netbeans 6.7.1 with memory options set to use up to 512MB - but it's never gone up that far before. And I've checked the size of the buffer on all three computers and they are all the same.
Does anyone know what the issue could be or how to resolve it? I am using JDK6 if that matters. Thank you for your time.
Edited by: Sengin on Sep 18, 2009 9:40 PM

Thanks for your answer. I'll try that.
I figured it had something to do with Windows 7 since it technically hasn't been released yet (however I have the RTM version thanks to a group at my univeristy in cahoots with Microsoft which allows some students to get various Microsoft products for $12).
Edit: I just changed the Clip to a SourceDataLine (and the few other necessary changes like changing the way the DataLine.Info object was created) and wrote the whole buffer into it, drained the line and then closed it. It works fine. I'll mark the question as answered, however that may not be the "correct" answer (perhaps it does have something to do with Windows 7 and not being completely tested yet). Thanks.
Edited by: Sengin on Sep 21, 2009 8:44 PM
Edited by: Sengin on Sep 21, 2009 8:46 PM

When editing a wiki page, get a 'request entity too large' error message.

[https://stbeehive.oracle.com/teamcollab/wiki/Sales+Playbooks:Demonstrating+Differentiators|https://stbeehive.oracle.com/teamcollab/wiki/Sales+Playbooks:Demonstrating+Differentiators] I'm trying to edit one of my wiki pages that has been static for about 5 months now, and when I try and save the page, I get the following message (note I cropped some because of formatting issues when posting):
*413 Request Entity Too Large*
HTTP/1.1 413 Request Entity Too Large Date: Tue, 18 Oct 2011 15:35:41 GMT Server: Oracle-Application-Server-10g Connection: close Transfer-Encoding: chunked Content-Type: text/html; charset=iso-8859-1
Request Entity Too Large
The requested resource
/teamcollab/wiki/<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta content="text/html; charset=utf-8" http-equiv="Content-Type" /><script type="text/javascript"> var U = "undefined"; var gHttpRelativeWebRoot = "/ocom/"; var SSContributor = false; var SSForceContributor = false; var SSHideContributorUI = false; var ssUrlPrefix = "/splash/"; var ssUrlType = "2"; var g_navNode_Path = new Array(); g_navNode_Path[0] = '1790'; g_navNode_Path[1] = 'splash_collabsuite'; var g_ssSourceNodeId = "splash_collabsuite"; var g_ssSourceSiteId = "splash";</script><script id="SSNavigationFunctionsScript" type="text/javascript" src="/ocom/websites/splash/sitenavigationfunctions.js"></script><script id="SSNavigationScript" type="text/javascript" src="/ocom/websites/splash/sitenavigation.js"></script><script type="text/javascript">var g_strLanguageId = "en";</script><script type="text/javascript" src="/ocom/resources/wcm/sitestudio/wcm.toggle.js"></script><script type="text/javascript" src="/ocom/resources/sitestudio/ssajax/ssajax.js"></script> <script id="ssInfo" type="text/xml" warning="DO NOT MODIFY!"> <ssinfo> <fragmentinstance id="fragment1" fragmentid="universal-metatag" library="server:UNIVERSAL-FRAGMENTS"> </fragmentinstance> <fragmentinstance id="fragment2" fragmentid="ExternalSiteCatalystFragment" library="server:EXTERNALSCFRAGMENTLIB"></fragmentinstance> </ssinfo> </script> <meta name="GENERATOR" content="MSHTML 8.00.6001.18904" /><title>Collabsuite Outage</title><meta name="Title" content="Collabsuite Outage"><meta name="Description" content="Collabsuite Outage"><meta name="Keywords" content="Collabsuite Outage"><meta name="robots" content="NOINDEX, NOFOLLOW"><meta name="country" content=""><meta name="Language" content="en"><meta name="Updated Date" content="4/12/11 10:38 AM"> </head><body> <!--SS_BEGIN_SNIPPET(fragment1,code)...
does not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit.
Additionally, a 413 Request Entity Too Large error was encountered while trying to use an ErrorDocument to handle the request.
The page, should you wish to eyeball it, is at:
https://stbeehive.oracle.com/teamcollab/wiki/Sales+Playbooks:Demonstrating+Differentiators

Duane,
This looks like the URL has the content of a wiki page as an attachment to the URL which is blowing up the get request. Can you go to the earlier version - the history should allow you to backtrack changes - if you access this earlier version and change something small - does it save OK. If so then maybe the change you made is the problem.
I cannot access the workspace without being given explicit access so this is a guess.
Phil

Playing a large Clip and "Requested buffer too large" exception

Hi All.
Through JavaSound, I am trying to reproduce a WAV audio file that I create within my application. Also the recording/acquisition of the audio file is performed through JavaSound.
The WAV audio file that I am trying to play has the following features:
- 44 Khz, 8-bit, mono
- Length = 1min 36sec
- File size = 4.04 MB
Here is a fragment of my code:
// Get the input stream from the input audio file
audioInStream = AudioSystem.getAudioInputStream(inputFile);
AudioFormat audioFormat = audioInStream.getFormat();
// Compute the buffer size (for a 0.25 seconds buffer)
float bufferTime = 0.25F; // 0.25 seconds of buffer
int frameSize = audioFormat.getFrameSize();
float frameRate = audioFormat.getFrameRate(); // frames per second
int numOfBufferedFrames = (int)(frameRate * bufferTime);
int bufferSize = frameSize * numOfBufferedFrames;
// Create the output data line
DataLine.Info sourceDataLineInfo = new DataLine.Info(Clip.class, audioFormat, bufferSize);
sourceClip = (Clip)AudioSystem.getLine(sourceDataLineInfo);
sourceClip.addLineListener(this);
// Prepare the output line for playing
sourceClip.open(audioInStream);
// Start playing
sourceClip.start();This code works perfectly fine on Windows (I am testing on a Windows XP Pro 32-bit machine).
On the other side, this code throws the following exception on Mac OS X:
javax.sound.sampled.LineUnavailableException: Failed to allocate clip data: Requested buffer too large.
     at com.sun.media.sound.MixerClip.implOpen(MixerClip.java:561)
     at com.sun.media.sound.MixerClip.open(MixerClip.java:165)
     at com.sun.media.sound.MixerClip.open(MixerClip.java:256)
     at mypackage.AudioPlaybackThread.run(AudioPlaybackThread.java:70)
     at java.lang.Thread.run(Thread.java:637)The exception is thrown upon the sourceClip.open(audioInStream); call.
Googling around, I discovered that the MixerClip implementation seems to have some inherent buffer size limitation of 1 MB... Isn't it ridiculous?
But why this is working perfectly fine on Windows - even with clips of 4 megabytes -, while not working with larger clips on Mac OS X?
Also, will the following code line influence the size of the buffer used by MixerClip?
DataLine.Info sourceDataLineInfo = new DataLine.Info(Clip.class, audioFormat, bufferSize);I know that I could use a SourceDataLine class, and write() data into it in order to reproduce my long audio clip, but I need support for pausing, seeking audio to a specific position, seeking forward, etc., and using a Clip would be absolutely perfect for this purpose!
Any help or suggestion would be greatly appreciated.
Thanks,
Marco

Googling around, I discovered that the MixerClip implementation seems to have some inherent buffer size limitation of 1 MB... Isn't it ridiculous?
But why this is working perfectly fine on Windows - even with clips of 4 megabytes -, while not working with larger clips on Mac OS X?Because Apple changes stuff in the JRE and Microsoft doesn't... and I personally believe Mac specifically strips down the JavaSound stuff because of iTunes (anti-competition and such).
Also, will the following code line influence the size of the buffer used by MixerClip?Probably not, no.
I know that I could use a SourceDataLine class, and write() data into it in order to reproduce my long audio clip, but I need support for pausing, seeking audio to a specific position, seeking forward, etc., and using a Clip would be absolutely perfect for this purpose!You can program that functionality yourself, and if you want to open large files in Mac, it sounds like you'll have to.

Keep getting 413 Request Entity too large for only one website

When I go to www.stapleseasyrebate.com my computer goes nuts and then I get a 413 Request entity too large. It only seems to be this one website.

This issue can be caused by corrupted cookies or cookies that are blocked.
*check the permissions on the about:permissions page and in "Tools > Page Info > Permissions"
Clear the cache and remove cookies only from websites that cause problems.
"Clear the Cache":
*Firefox > Preferences > Advanced > Network > Cached Web Content: "Clear Now"
"Remove Cookies" from sites causing problems:
*Firefox > Preferences > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"

Sync error: Uploading records failed: "client issue: request body too large"

1328917629619 Sync.Engine.AdblockPlus DEBUG Uploading records failed: "client issue: request body too large"
This happens from 2 Win 7 computer and 1 Win XP computer sync'd. Without the Add Block Plus being sync'd everything works.

Hi!
That's a problem with the Add Block Plus sync engine. It seems that they have issues on their servers.
Try to ask the same question in their forum: https://adblockplus.org/forum/
Good luck!

Invoking service from OSB throws Request Entity Too Large fault

Invoking .net service with large(>1M) base64Binary field from OSB returns "BEA-380000:Request Entity Too Large" error.
How to enlagre the maximum message size?

You have to slightly adjust WebLogic configuration:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_wls/web_server.html#wp1059784

Request Entity Too Large?

What does "Request Entity Too Large" mean? It keeps preventing me from seeing ANY of the posts I try to open.

Try clearing your cache and cookies in the browser. That should temporarily fix the problem until lithium comes up with a permanent fix.
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

413 Request Entity Too Large

When importing an APEX 2.2 application in APEX 3.1 there is an error:
The requested resource
/pls/apex/wwv_flow.accept
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.

Hello WebMees,
Ok, then you might have a look at your database alerts and configuration.
Which database are you using?
Regards,
Dimitri
-- http://dgielis.blogspot.com/
-- http://apex-evangelists.com/
-- http://apexblogs.info/

I get error 413 - Request Entity Too Large on 2nd or 3rd found search

Situation - Looking at Newspaper website
I have received the message after looking at other articles. I logged off Firefox, logged back on went to the article, wqas able to read it, went to a second article, got the error. I had only one window open.

This issue can be caused by corrupted cookies.
Clear the cache and cookies only from websites that cause problems.
"Clear the Cache":
*Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
"Remove Cookies" from sites causing problems:
*Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"

Eu entrava em um site normalmente, mas aí apareceu esta mensagem do nada "Request Entity Too Large A request entity is longer than the server can handle."

Faz uns 2 dias que eu jogava um jogo do site, mas quando eu fui entrar de novo, apareceu essa mensagem... o que está acontecendo?

Yes, Long standing problem with Verizon which does not support Google...go figure. To log in to Verizon using Google, you must access it throuugh an "incognito Window" which you can access by right clicking on the google icon. This has been reported by many for over a year but verizon still has not fixed it, they just don't care. There are othe ways around it which I posted previously, but this is the quickest.

Since upgrade to iOS 7 Email error on over 100KB emails "Cannot Send Mail The message was rejected by the server because it is too large." Connecting to Exchange via Activesync

Hi,
Following the upgrade to iOS 7.0.3 on all our iPhone and iPad devices, it has been identified that when sending emails around 100KB in size and over an error message appears on the device stating “Cannot Send Mail The message was rejected by the server because it is too large.” See error message below. The send/receive limit is over 10MB so this is not the issue.
We are in an Exchange Environment using Microsoft Activesync. This issue is not evident in iOS 6. This has been tested on an iPhone 3GS running version iOS 6.1.3. We have been unable to repeat the issues seen on iOS 7 on the older OS. It is not possible to roll back to the older operating system as Apple are no longer signing the software.
We use Microsoft Active Sync to connect to our Exchange servers through a TMG. The issue is very inconsistent, some identical emails go through, some fail. This is not an issue with the send/receive limit as this is over 10MB. The error message when it fails on the TMG is Status: 413 Request Entity Too Large, which we believe is from IIS on the CAS server.
Does anyone have any suggest course of actions to take?
Many Thanks

This resolution have to attend at the server not with the ios device. My employer's mail administrator reject me to correct it from the server. As his concern is, if ither ios devices works why don't mine? So I am helpless than changing my iphone. It works fine for early versions of ios and with androids. And also one of my friends iphone4 with ios 7 (similar as mine) works too. So I guess it's something wrong with my iPhones settings. But basic question I cannot understand is it works in my phone before this ios7 upgrading. And currently working with my yahoo account too. Favourable reply expected.

USB Printing - client-error-request-value-too-long

A little while back, my iSight suddenly stopped working and so I did a full format and reinstall to 'fix' the problem. The problem wasn't 'fixed' through this action. Instead, I had to disconnect power and let the computer sit there for a bit and think about what it had done (naughty iMac). Anyway... Another USB-related problem just popped up - this time with my printer.
The printer is a Canon IP4000 and I just installed the latest drivers to try to fix this error. The first error was something about not being able to write to the device. I thought that was stupid and would probably be fixed by deleting the printer and then reinstalling it. I have so far 'uninstalled' the printer (more or less just removed it from the printers list in the printer utility) and now I can't re-add it to the list to install it. The error reads as follows:
An error occurred while trying to add the selected printer.
client-error-request-value-too-long
I have tried Google but I just don't have the time to sort through all kinds of explainations on how CUPS works on Linux (apparently, this error is related to CUPS in some way). I also tried searching the forum for the error message but found nothing. So here I am again asking for some help from those who might have seen this problem before.
This is on a fresh install and I have tried it on newly created users to no avail.
Thanks for any help! -Thomas

I've recently had this error which came up because the spool folder was missing. In the terminal:
sudo mkdir /private/var/spool
sudo mkdir /private/var/spool/cups
puts the proper folders in their place. Repair permissions afterwards.
Through the cups web interface, the error is "Request entity too large"
Panther has the same folders, but a different error comes up.
The above cups folder has different permissions than the default. Probably the same for Tiger and Panther but just to be safe, repair permissions.

Request-URI Too Large

Similar Messages

Maybe you are looking for