DevForce Community Forum : Is maxRequestLength relevant any more? http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce Classic : Is maxRequestLength relevant any more? Sat, 11 Apr 2026 01:09:20 -700 Fri, 16 Aug 2013 17:39:24 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=4278 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Is maxRequestLength relevant any more? : Yes, it's the "httpRuntime... http://www.ideablade.com/forum/forum_posts.asp?TID=4278&PID=16745#16745 Author: ctoth
Subject: 4278
Posted: 16-Aug-2013 at 5:39pm

Yes, it's the "httpRuntime maxRequestLength" in <system.web>. I think I know what confused me: it's in KiloBytes. Our settings is now "1648576", which then means ~1.6GB, and not 1.6MB :)
]]> Fri, 16 Aug 2013 17:39:24 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=4278&PID=16745#16745 Is maxRequestLength relevant any more? : Interesting. I assume youmean... http://www.ideablade.com/forum/forum_posts.asp?TID=4278&PID=16743#16743 Author: kimj
Subject: 4278
Posted: 16-Aug-2013 at 5:29pm

Interesting.  I assume you mean the maxRequestLength on the httpRuntime element, and in theory it should kick in when using .NET Remoting with IIS, but I'm seeing the same results as you.
 
There's little documentation on Remoting, and Remoting in IIS, and I can't find anything that explains whether this should work or why it's not.   There have been no enhancements to DevForce which would have affected this.
]]> Fri, 16 Aug 2013 17:29:25 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=4278&PID=16743#16743 Is maxRequestLength relevant any more? : In a BOS setup there&#039;s a... http://www.ideablade.com/forum/forum_posts.asp?TID=4278&PID=16741#16741 Author: ctoth
Subject: 4278
Posted: 16-Aug-2013 at 3:56pm

In a BOS setup there's a "maxRequestLength"settings in the BOS server's web.config file. I wanted to challenge this limitation, and purposefully created transactions, where I persisted bigger entities than the maxRequestLength into the database. Each transaction had such a single entity, which stored big binary data in a single field. Interestingly, no error was triggered, and I confirmed with Fiddler that data sent up in one big piece.
I wonder what are the situations where "maxRequestLength" poses real limitation? Were there any enhancement in DevForce Classic versions which changed the behavior in this respect?
We use RPC (and not WCF) for client-BOS communication. Earlier we used v3.7.1, I'm testing now with v3.8.2.

Thanks,
Csaba
]]> Fri, 16 Aug 2013 15:56:55 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=4278&PID=16741#16741