I'm trying to force all views in my ASP .NET Core 3.1 MVC project to use http only as I only bound http on my local testing server. However, my views only try to load resources from the https link, and that does not work. When I debug locally from my local development PC, it is also set as http only and that worked. Does anyone have any idea why it does not use the http links while on Windows Server 2016 side?
Related
Is there any safe way to host a site Net core website through a installer (may be in IIS), similar to any desktop application installer?
e.g. Neo4j works as webservice but has its own jetty server to host. U just download and its up and working.
I dont understand your problem. Why you just dont run your app with Kestrel? (dotnet <patch_to_your_dll)
I have two questions about servers of VS Express 2015 for Web
First at all, it's dissappeared an option for change from IIS server to native Developer Web Server from project options. Is it due to Express version or could I install it?
Second problem is with URLs of IIS server. I didn't change default settings but my url:
http://localhost:51734/PROJECT_FOLDER/SUBFOLDER/PAGE.aspx
trims into
/SUBFOLDER/PAGE.aspx
I know somewhere in IIS settings I can customize the URL, but I want my URL without changes.
EDIT: I should say it trims SOMETIMES into that URL
Does anyone have any experience with creating URL rewrites in Webmatrix? Because it uses IIS Express instead of IIS 7, there's nowhere for me to create these rules.
I am deploying to IIS 7 on my production server, so if I need to do any rewrites, I need to make them directly in production to test.
Is there any way I can switch to using IIS instead of IIS Express on my local machine?
I have tried a few things to get local IIS working, but to no avail.
You can install IIS on a Windows 7 or Windows 8 machine by going to Control Panel -> Programs and Features -> Turn Windows features on or off. Make sure to install enough of the components to get a WebMatrix site working - ASP.NET & the management console for certain.
You can then create a virtual server for the directory your project is in and use the IIS management console to play around with URL rewriting. You may need to install the UrlRewrite module using the MS Web Platform Installer, available here:
http://www.microsoft.com/web/downloads/platform.aspx
If you need more help getting your local IIS working, give me some more information on how far you've got and I'll try and extend my answer.
I have an MVC3 web application - it is a set of controllers and views without any DB access at the moment.
In the properties for the WEB App (in vs2010 Sp1) If I select
Use Visual Studio Development Server defaulting to a port 10905 then the app works great from an f5
If Instead I use local IIS WebServer with Use IIS Express ticked my project url is http://localhost:10905/ and the app works great.
But if I use local IIS WebServer with Use IIS Express NOT ticked my project url is
http://localhost/TunnelRats then f5 does not work - I literally get a browser popping up with no content displayed just the url address populated.
I created the virtual Directory (using the create directory button) and looked in the IIS Manager
The IIS Manager uses pool ASP.NET v4.0 which has enable 32 bit apps set to true and an integrated pipeline mode.
If I browsse directly from the virtual directory I get the same problem.
Its seems my IIS has a problem where my IIS express does not have a problem running my MVC 3 app.
I used aspnet_regiis -iru to reinstal v4 into IIS with no effect.
Any Ideas
thanks
Martin
might be that you do not have dynamic content enabled on you IIS.
Easiest way to set up IIS for asp.net this days is to use Web Platform Installer
Do you do local development/debugging with the internal webserver or a local iis install? I'm currently running the internal VS2010 webserver but it's so slow it hurts. I can see the page rendering in front of me...
I prefer to use Windows Server 2008 as my development machine so that I can use IIS 7 as the web server and just set the default location of the website to a locally mapped DNS name. This especially helps when testing code that is dependent on domain URIs and other information of that nature.
One problem I have experienced is an intermittence in the ability of studio to bind the debugger to the IIS processes. (sometimes a reboot is required to get studio to bind if this happens)