Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 3 years ago.
Improve this question
My application looks fine when I run on the localhost via visual studio but it creates mess when I publish it on the AZURE Web App Service. I am using free tier of Azure web app service.
Image of the header of homepage at the local host
Image of the header of homepage at the Azure web app-service
Home page items at the localhost
Home page items at azure web-app-service
Button at the homepage at localhost
Button at azure web-app-service
My link to the site is https://auctionit.azurewebsites.net/
If you check the console tab, you'll see that some files were not properly loaded. I believe this is why the layout is broken, no problems on Azure side.
Nothing to do with the Azure free tier.
From what you have shown here, this is something to do with the styles. Check your css and inline styles. Make sure all the css and other style related resources are deployed correctly.
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 9 months ago.
Improve this question
I created a Web API project in which the webpage on which I want to display the response from the API is not working. The web page shows "This page isn't working HTTP ERROR 405".
I searched a lot on Google and YouTube to "How to resolve HTTP ERROR 405", but I was unable to find the right content to fix this issue.
How can I solve this issue?
Here is my Web API GitHub repository link: https://github.com/ansu647/CoWIN-sample
A 405 error indicates when a user requests to access a web page and the web server receives & accept that HTTP method, but unfortunately the server reject that HTTP method so the user can’t access the web page. This causes the error in the user's page. To fix this:
Go through your code. It may be it has bugs (or)
Shift your application logs and server logs (or)
Check the web server configuration file
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question appears to be off-topic because it lacks sufficient information to diagnose the problem. Describe your problem in more detail or include a minimal example in the question itself.
Closed 8 years ago.
Improve this question
My .asp page is in the folder named "MyWeb", and "MyWeb" folder is under wwwroot folder which is under inetpub. I also added MIME types in IIS Manager for .asp as application/asp, and for .aspx as application/aspx I tried it a long but still it is not working. When I go to open that .asp file it is asking for download in IE browser and displaying a blank page in Mozilla Firefox. Please can any body tell me how to solve this issue?
ANSWER=
Issue solved I just changed the setting in IIS Manager set Enable Parent Paths to true and Send Errors To Browser to true and it happened. Localhost Home Page of IIS was displayed and my asp scripts are also running.
It possible that you haven't got Classic ASP support installed in IIS. To do this in Windows 7 follow the steps below;
How to enable Classic ASP support on IIS for Windows 7
Installing Classic ASP support
Goto Control Panel -> Programs and Features
Select from the left navigation bar
From the Windows Features dialog expand Internet Information Services -> World Wide Web Services -> Application Development Features and tick the option ASP this will also tick ISAPI Extensions if not already ticked (see image).
Configuring IIS Web for Classic ASP
Open Administrative Tools -> Internet Information Services (IIS) Manager and select the website you wish to configure.
In Features View under the IIS section select Handler Mappings check the existing mappings list that appears for a handler that points to *.asp if one doesn't exist select Add Script Map from the right hand navigation bar.
Fill in the options as per the below image
IMPORTANT If using 64-bit and want to enable 32-bit support you may wish to use the 32 bit equivalent ISAPI DLL. See Dee's answer to How to enable ASP classic in IIS7.5
Select the Request Restrictions button to open Request Restrictions dialog. The three images below detail the values that should be configured if not already set.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
Hi All,
Actually I have a web application build using classic asp and vb script, along with MS-Access 2003 hosted on IIS 6.0. It is running fine.
Now I have shifted it to on IIS 7.0 and database MS-Access 2003 to 2010.
The Login Page is running fine, and also it's easily get login when I try to login. But after login when I try to access some others pages through click a button, it shows error 500 Internal Server Error.
I have given security this application to the everyone level but still it is showing error.
I am using database through DSN. I can not say that there is any DSN configuration error or mistake I did, because login page is working fine which gets user id and password from my database.
What type of issue might be there?
solved. Now I have given my Intepub\mailroot\pickup forder to appropriate permission.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 13 years ago.
Improve this question
I have a problem accessing an intranet website with IE8. I can access the site through Firefox or any other browser, except IE. IE will prompt for a username and password but never accepts the credentials and just shows a 401 message, "You are not authorized to view this page"
The website is configured as follows:
Windows Server 2003
IIS Directory Security > Authentication Methods > "Integrated Windows authentication" only
Any ideas?
Sounds like an IE security setting. I'd check two things in options:
In the Advanced tab, in the security section, is Enable Integrated Windows Authentication checked?
In the Security tab, does the site come up under the Local Intranet zone? If not, add it. Also, make sure the User Authentication item under custom settings is set to one of the Automatic Logon options (checking Automatic Logon with current user name and password should make the browser automatically log into the site).
A good place to start when troubleshooting 401 errors in IIS is this Microsoft guide
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 14 years ago.
Improve this question
I have an .asmx in a folder in my application and I keep getting a 401 trying to access it.
I have double and triple checked the setting including the directory security settings. It allows anonymous. I turned off Windows Authentication.
If I delete the application and the folder its in, then redeploy it under the same application name it magically reapplies the old settings.
If I deploy the exact same application to a different folder on the server and create another application under a new name and set up the directory security setting again it works!!!
How do I get IIS to forget the setting under the original application name?
After deleting the first application in IIS and its associated files on the disk, try restarting IIS (or your server if possible). Then come back and recreate the whole setup.
Eventually I got it working again. By deploying to a different folder and recreating the virtual folder / application to it.
I am not sure how that makes a difference but at least things are working again.
I ran into a similar situation with asp.net pages. I had Anonymous on and Integrated off for a virtual directory, but one page was the opposite. Everything worked fine until I went to the one special page, then my post backs stopped working and I couldn't log out of the site until I deployed to a new virtual directory.
My eventual solution was to enable anonymous and integrated for the entire site and just turn off anonymous on that one page.