I have an old ASP classic application that gives the following error when accessed by some browsers.
Active Server Pages error 'ASP 0131'
Disallowed Parent Path
We confirmed that the checkbox for accessing parent directories using ".." had been checked for this IIS site/application. There is no problem accessing the pages on my desktop using Chrome; however on my laptop, using the same version of Chrome, I get the above message from the server.
From the same Windows 10 laptop, I can navigate the site fine using the Microsoft browser. Ultimately, I may have to edit the pages to get rid of the ".." in the application but would like a fix in the meantime.
Related
After yet another reboot of my macbook, chrome stopped loading my webapp.
It returns literally nothing in browser window and the only thing i managed to find is that requests in chrome's timeline has status "cancelled".
If I'm trying to get there from another website (by changin url and hitting "return" button), it also does nothing, it doesn't even try to reload page.
Other browsers load it fine atm.
I've received this report from a user about couple of weeks ago, but now i've got it myself, so I assume the problem is in my server.
Recently, i've found that my android phone also can't access the website from chrome browser. The behaviour is the same. However, android default browser has access.
What could that be? Where should i look?
I'd provide more information, but there is no error codes or messages of any kind, so i have no idea what information could help in this question.
Also, i have a chrom browser extension (similar to Pocket), which also is unable to access server. The notable difference is that extension uses Socket.io only.
There were no recent code changes on server side except letsencrypt certificate renewal.
I've tried this:
server restart
different ip/locations (vpn and public access points)
chrome data cleanup / chrome version degrade / chrome reinstallation / chrome canary installation
tried to open server address directly - no difference
Now we build a site with sharepoint 2013. Per our customer requirement, we need to support IE8. But my develop environment is IE11(in windows server 2008R2), so I decide to degrade my IE version.
In the beginning, I can use IE11 to access the website which I created in share point. But after my degrading operation, strange things happened: I enter the url in the IE8, it is loading... seems every thing is fine, I can see the background pictures be downloaded in the browser,but few seconds when it loading completes(I guess), it redirects to the 404 error page.(normal page flash to the 404 error page) And I tried to use Chrome to visit this site, every thing works.
I also set the IE security level to low, and trun off IE ESC(enhanced security configuration), it doesn't work.
BTW, the IE8 can access the url: myMachineName/_layouts/15/start.aspx#/SitePages/Home.aspx
So I guess I need to add or change some configurations in the website which I created in the sharepoint to fit IE8.
Many Thanks!
This is my setup.
I am running a local web server on the network (windows 7/IIS7) and I have a dedicated server with a hosting provider (Windows 2008/IIS7.5)
When I upload the website (ASP.net MVC 3.0) to the local server I can access if correctly in all browser (IE7/IE8/FireFox/Chrome).
When I upload the website to the dedicated server I can access the site correctly with (IE8/FireFox/Chrome) and it renders correctly, but it does not render correctly in IE7 it appears as if the CSS are not being downloaded.
I installed Fiddler and confirmed that the same files (css/js) are being downloaded with IE7 as with the browser. I also compared the browser source of IE7 with the other browser and there was no difference.
At this point I am totally stumped as to why IE7 would not work with the dedicated server while it works for the internal server. (Note that both servers work fine for all other browsers).
Final notes
for the internal server I access the website as
http://192.168.0.160/
for the external server I access the website as
http:/domain_name/
Any insight, ideas, hunches would be greatly appreciated.
Try putting the following tag in your <head></head> section:
<meta http-equiv="X-UA-Compatible" content="IE=8">
I've had similar problems with IE 8 rendering pages as IE 7, etc. The X-UA-Compatible meta tag forces IE 8 to render as IE 8. You can also use it to force it to render in compatability mode as well.
The issue turned out a security issue on the production server. The css file did not have the correct permissions and hence where not downloaded by the browser. Fiddler picked up on it by I didn't clue in right away.
I generated a new web site in IIS. Under the new web site, there are some asp .net 2.0 applications. Tomcat is also running on the same server and they are working correctly.
But when I try to open an asp .net application, I am taking page can not be found error message. Then I changed the configuration settings of asp .net version from 2.0 to 1.1 then it is not giving page can not be found message but it gives an error message about web config. What can I do?
You haven't given many details. This could be a couple of things:
you have used an incorrect URL
you have used an incorrect protocol (i.e. http instead of https)
you are specifying a directory but you have no default document set up (i.e. you are going to http://mywebsite/myvirtualdir/, but you have no default.aspx)
you haven't installed ASP.NET so there are no handlers for aspx pages
until you give more details then no-one can say for sure what your problem is.
Good Morning,
I was having serious problems regarding this website.
What happens is everyytime I try to open a .shtml page in the site it always has an error "The Page Cannot Be Found" but this is highly unlikely since I already all have the resources in my local pc and already did a virtual directory for the entire site. Can you please tell me what's the problem? i've checked all the codes and they're constructed just fine.
If you're attempting to view the page in Internet Explorer then I recommend turning off friendly HTTP error messages in the advanced settings. Disabling the setting may result in more verbose error messages, especially if it's an HTTP/500.
This is not actually an ASP problem. .shtml files are handled by the server-side include ISAPI application extension.
In Web service Extensions folder under the server icon in IIS manager, ensure that Server Sice Includes is set to "Allowed".