Print Page | Close Window

Is maxRequestLength relevant any more?

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=4278
Printed Date: 25-Apr-2025 at 3:01am


Topic: Is maxRequestLength relevant any more?
Posted By: ctoth
Subject: Is maxRequestLength relevant any more?
Date 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


Replies:
Posted By: kimj
Date 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.

Posted By: ctoth
Date 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 :)


Print Page | Close Window