• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

web.config parsing errors

M

MainSoft

Guest
Hi,

My web hosting service (ikoula) is using Plesk 8.1 and I have noticed a bug in Plesk when configuring my ASP .Net application.

This bug (which costed me hours of debugging until I understood what was going on) is related to setting the trust level from the Plesk page. When you change this setting, Plesk opens the web.config file and looks for the <system.web> tag under which it will insert a <trust level="xxxx" /> tag. However, the parser doesn't seem to be aware that <system.web> tags can soemtimes be found not only under the <configuration> root tag but also at other locations in the web.config file. For example, the web.config file for "ASP .Net Forums 2.0" (an old ASP .Net 1.1 app) has multiple sections like this:

<configuration>
...
<location path="EditPost.aspx">
<system.web>
<authorization>
<deny users="?" />
</authorization>
</system.web>
</location>
<location path="PrivateMessage.aspx">
<system.web>
<authorization>
<deny users="?" />
</authorization>
</system.web>



In that case, Plesk inserts the <trust level="xxxx" /> at the wrong place (under one of the <location> tags) and re-read it from there.

So when you look at the Plesk page for ASP .Net settings, you think that you are have set the trust level to xxx but it is actually not the case.

So the parser should check at which level in web.config it found the <system.web> tag that it will modify because this tag is not necessarily unique.

Best regards.
 
Very old thread indeed but I discovered today that this error still persist in Obsidian RC4 which is a bit disturbing.

Workaround: add these lines at the top of web.config:

<location path="NonExistent.aspx" allowOverride="false">
<system.web>
<authorization>
<deny users="?" />
</authorization>
<trust level="Full" />
</system.web>
</location>

The Plesk can write whatever trust level it wants there instead, which of course will be ignored.
 
Back
Top