I have a web api application (net core 2.1.1) with odata protocol.
Everything works fine in Visual Studio 2017 (response is ok over https), but after I've deployed it to my local IIS website (with https binding), I have a ERR_CONNECTION_RESET 200 in Chrome using get request like https://localhost:5001/odata/Products.
Related
I run into some serious problem.
I have a windows server 2008 R2 Enterprise. (Version : 6.1.7601 Service Pack 1 Build 7601)
and IIS version 7.5.
I have publish my angular application on this IIS and bind it to the https:xxxx.domain.com
and localhost:9090.
The website is running on "localhost:9090" or XXX.YYY.ZZ.13:9090 properly.
But the website is not running from outside when hitting the URL "https:xxxx.domain.com".
When hitting on the URL getting below
503 - Service unavailable.
403 Forbidden unauthorized access
After several refresh it opening my another website published on same machine.
I have created my subdomain on cloudflare.
I have tried all the Stack-Overflow solution but nothing is working in my case.
I have a problem where a site runs okay on hosting server browser but not on my local browser.
It is a site I need to migrate from a windows 2012 server to a new windows 2019 server. I have ensured all IIS components are setup on the new Windows 2019 server. I copied over all files and re-created the site in IIS on new server with, as far as I can see, exactly the same IIS configurations except the Connection string is set to database on new server which was also migrated from old server. I have checked the websites root folder permissions are the same too
The site is built in ASP.NET and both ASP.NET authentication and windows authentication are enabled and anonymous authentication is disabled. The application pools' "identity" is set to "ApplicationPoolIdentity" as was the old site.
To ensure the site worked on new server I created a registry entry for "DisableLoopbackCheck" because the site continually asked for credentials and with registry change my credentials were accepted and site appeared
Lastly, I have asked ICT to ensure the local DNS is set to new site and the old site in old server is stopped. However I still continue to receive "HTTP Error 404. Resource not found" in both Edge and Chrome. I have also viewed the IIS logs for site but tell me very little
Why do I keep getting this 404 error please? I feel it is something simple I am missing
I publish my Web API application to IIS server 8.5 (running on Windows Server 2012), but the performance is not good. If I run Web API by dotnet myapi.dll (pure Kestrel Http Server), the performance is good.
Client to IIS
Client to Kestrel
Content download time is slow if the web API run on the IIS. If connect from the localhost looks like work normal.
Is it possible to tune the performance? Or this is IIS limitation?
I have developed a web api with HTTPPATCH. I am using Fiddler to test the web api. In my local host I am not facing any issue and able to process patch request successfully. But when I am hosting the same in 2008 R2 server where my IIS version is 7.5. I am not able to process Patch request using the fiddler. I am getting error code 400, Proxy server closed.
Additionally I have GET, POST and DELETE request as well. These request are able to process successfully.
Deployment to IIS Server:
1.) Set up your IIS correctly.
2.) Check username credentials folder permission.
3.) check application pools framework for your project after your project paste into IIS server.
4.) Check Browsing Directory if enabled.
Hope it helps.
I used HTTPS with PORT 443 instead of HTTP for PATCH request and Its working as expected.
https://support.appharbor.com/discussions/problems/83648-odata-web-api-2-patch-not-working
I have been using an open source WebDAV framework named "Sphorium" for quite some time to talk to my data repository.. I have been using Cassini web server to host my WebDAV server module and everything was working just fine if I map the server as a web folder in my system. However, i found that Cassini web server does not support "https". So, I started looking out for deploying my WebDAV server application in IIS.. So I built a website in ASP .Net which talks to the Sphorium WebDAV module and authorizes the user. And when I run my website using the VS Debugger, it gets hosted on the ASP .Net development web server, prompts for the credentials and works just fine. However, if I publish my web app and try to host in in IIS, and try to browse, it prompts me for the password for 3 times and finally says "Unauthorized"...
Could someone pls throw some light on how I can use IIS in this case? Do I have to give any permissions?