Why is the /eurl.axd/Gibberish binding attached to the end of my pages?

I worked to ensure that our site switched to a public beta server, and after we configured IIS to match the internal testing server, I noticed this problem. The app is still working, but it has this ugly stuff at the end.

What causes this? I installed the ISAPI filter and added a template for aspnet_isapi.dll.

Refresh.

I completely deleted and updated my site on my test server to check how the URLs looked.

After rebuilding the site for beta compliance, my test server does not display any of eurl.axd / gibberish in the url.

Below is a brief overview of the configuration.

IIS6 / Windows 2003 / Helicon Isapi rewrites the work.

Website <- asp classic | Default Application Pool | custom .htaccess file
|
|
+ ----------- dr405 <- application MVC3 | .Net 4.0 App Pool

As far as I know. beta reflects this for sure. However, let me say that this is not so. What change might cause the problem?

Since the site runs on one server and not on another, I would prefer not to have any decisions related to changing my application, editing my .htaccess file, etc.

Web.config system.web section

<customErrors mode="Off"/> <httpRuntime maxRequestLength="1000000000" /> <compilation debug="true" targetFramework="4.0"> <assemblies> <add assembly="System.Web.Abstractions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add assembly="System.Web.Helpers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add assembly="System.Web.Routing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add assembly="System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add assembly="System.Web.WebPages, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add assembly="System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> </assemblies> <buildProviders> <add extension=".cshtml" type="System.Web.WebPages.Razor.RazorBuildProvider, System.Web.WebPages.Razor" /> </buildProviders> </compilation> <authentication mode="Forms"> <forms loginUrl="~/Account/LogOn" timeout="90000" /> </authentication> <membership> <providers> <clear /> <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ApplicationServices" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/" /> </providers> </membership> <profile enabled="true" defaultProvider="dr405ProfileProvider" inherits="Tangible.Profiles.DR405Profile"> <providers> <clear /> <add name="AspNetSqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ApplicationServices" applicationName="/" /> <add name="dr405ProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ApplicationServices" applicationName="/" /> </providers> </profile> <roleManager enabled="true"> <providers> <clear /> <add name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="ApplicationServices" applicationName="/" /> <add name="AspNetWindowsTokenRoleProvider" type="System.Web.Security.WindowsTokenRoleProvider" applicationName="/" /> </providers> </roleManager> <pages> <namespaces> <add namespace="System.Web.Helpers" /> <add namespace="System.Web.Mvc" /> <add namespace="System.Web.Mvc.Ajax" /> <add namespace="System.Web.Mvc.Html" /> <add namespace="System.Web.Routing" /> <add namespace="System.Web.WebPages" /> <add namespace="System.Data" /> </namespaces> </pages> </system.web> 

Update 2

Sorry if I embarrassed anyone. I have an integrated testing server. which is not exposed to the public. The site is working correctly. An external screen brand server is where I have problems. A production server is not yet a factor in all of this.

Update 3

Here is my .htaccess file. I still do not think that this should require any changes, since this file and application function are correct on my integrated testing server.

Most file targets are to fix some really ugly URLs, and users will automatically move the content. No rules are intended for the application I am having problems with.

 RewriteEngine On RewriteBase / RewriteCond %{HTTP_HOST} (www.sarasotaproperty.net|www.sc-pa.net|sc-pa.net|sarasotaproperty.net) [nc] RewriteRule ^(.*)$ http://www.sc-pa.com/$1 [R=301,NC,QSA] RewriteMap lc int:tolower RewriteCond %{REQUEST_URI} [AZ] RewriteCond %{REQUEST_URI} !.*(js|css|inc|jpg|gif|png) RewriteRule (.*) ${lc:$1} [R=301] RewriteCond %{REQUEST_URI} !.*(web_content/pdf/).* RewriteCond %{SCRIPT_FILENAME} !-d RewriteCond %{SCRIPT_FILENAME} !-f RewriteRule (?!.*/web_content/pdf/)([^/]*?\.pdf) /web_content/pdf/$1 [R=301] RewriteRule pasite-(.*\.asp)$ /content/$1 [R=301,QSA] RewriteRule home\.asp$ / [R=301] RewriteRule ^search/tpp/?$ content/search_tangible.asp RewriteRule ^search/?$ content/search_real_property.asp RewriteRule ^downloads/?$ content/downloads.asp #RewriteRule ^(.*?view)/([^/]*)/([^/]*)(/.+)? /search/parcel_detail.asp?account=0&$2=$3 [NC,LP,QSA,R=301] 
+4
source share
3 answers

When the virtual folders in IIS match those on the production server, it works as expected; however you see an odd url if different virtual folders?

It sounds as if the rewrite rules in .htaccess are specific to a production installation.

Can I make changes to helicon httpd.conf / httpd.ini on a beta server so that the rewrite rules work as expected? I'm not sure what the rule should look like, and some time has passed since I worked with something similar.: /

Here's the doc on httpd.ini: http://www.isapirewrite.com/docs/#conffile

A thread that is very similar to your situation that can help you in the right direction: http://www.helicontech.com/forum/15029-ASPNET_40_MVC_and_ISAPI_Rewrite_3.html

Once you configure the rewrite rule in httpd.conf, you may need to deny rules from .htaccess. I think AllowOverride None will do this. Here is an example:

 <Directory "/parentFolder/dr405"> AllowOverride None </Directory> 

My memory of httpd.conf and rewrites is sketchy at best. Hope this helps you in the right direction.

EDIT

Have you tried the suggestions given in the answer here: fooobar.com/questions/172934 / ...

It sounds very similar to the problem you are facing.

0
source

What version of session state are you using? It looks like session state information and it is set to cookieless.

0
source

What are the rules? Sometimes the "RewriteBase /" directive is the reason for different assemblies.

0
source

Source: https://habr.com/ru/post/1387245/


All Articles