New Posts New Posts RSS Feed: Is maxRequestLength relevant any more?
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Is maxRequestLength relevant any more?

 Post Reply Post Reply
Author
ctoth View Drop Down
Newbie
Newbie
Avatar

Joined: 04-Mar-2013
Location: Fresno, CA
Posts: 22
Post Options Post Options   Quote ctoth Quote  Post ReplyReply Direct Link To This Post Topic: Is maxRequestLength relevant any more?
    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 :)
Back to Top
kimj View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 09-May-2007
Posts: 1391
Post Options Post Options   Quote kimj Quote  Post ReplyReply Direct Link To This Post 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.
Back to Top
ctoth View Drop Down
Newbie
Newbie
Avatar

Joined: 04-Mar-2013
Location: Fresno, CA
Posts: 22
Post Options Post Options   Quote ctoth Quote  Post ReplyReply Direct Link To This Post 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
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down