A potentially dangerous Request...

If you have questions about using mojoPortal, you can post them here.

You may want to first review our site administration documentation to see if your question is answered there.

This thread is closed to new posts. You must sign in to post in the forums.
12/18/2010 10:29:08 AM
Igor-san
Gravatar
Total Posts 7
View Posts
In Jackpot We Trust

Re: A potentially dangerous Request...

and the mojoPortal package for .NET 4 does have this in Web.config so it would not throw that error:

<httpRuntime requestValidationMode="2.0" maxUrlLength="560" maxQueryStringLength="2048" />

Sorry for bad english. . I tried to install on the server with the .NET 4 new  release mojoportal-2-3-5-8-b, but only got 500 error. In the web.config there is no such line.

12/18/2010 11:48:04 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: A potentially dangerous Request...

This line does exist in the Web.config file of our packages for .NET 4. It will prevent some expected errors on postback but it will not prevent all possible causes of  "a potentially dangerous request".

500 is just a generic error code, to find out the real error detail see Basic Troubleshooting, there is a way to see error details. But if you install with the wrong version of dotnet then it may not even be able to load the Web.config file so you need to make sure your hosting is configured for .NET 4 (it must use a .NET 4 application pool).

Hope it helps,

Joe

12/18/2010 12:01:51 PM
Igor-san
Gravatar
Total Posts 7
View Posts
In Jackpot We Trust

Re: A potentially dangerous Request...

Thank you , to the web.config I figured out. It remains to deal with hosting, there is something not so configured.

12/20/2010 3:40:22 AM
Igor-san
Gravatar
Total Posts 7
View Posts
In Jackpot We Trust

Re: A potentially dangerous Request...

I find the advice in the forum http://forums.iis.net/t/1166889.aspx, adding in web.config a few lines sectionGroup.
And it worked. But strangely, I've installed version mojoportal-2-3-5-8-b-mssql-net40-deploymentfiles.zip and just on NET 4.0

In any way, it worked.

12/20/2010 8:15:56 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: A potentially dangerous Request...

Hi,

From reading that thread it sounds like in some installations it does not correctly read the machine.config file for .NET 4. That is a strange problem but is good to know it can happen and you can work around it by declaring the section in Web.config but in general if .NET 4 is installed and working correctly it should not need that declaration in Web.config and in fact if you put it there it will result typically in a duplicate section error under .NET 4 because it is declared in machine.config

In any case I'm glad you got your site working.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.