i have a web role with mvc 3 on azure with os 2 that is working fine - with ssl
I wanted to upgrade my project to mvc 4 with .net 4.5 so i created a new azure project and copy everything to a new project and everything worked on my station ( I have windows 8 with iis 8 like server 2012).
i upload the new project to azure - with os 3 and everything and my web site is working fine until the code need to create an ajax request with parameters - the ajax request is pending for a minute or so and then i get an error page.
when i remove the https to http the ajax request is working flawlessly.
after investigating and putting traceFailedRequests i saw that iis is rejecting those ajax request.
in the moudle ManagedPipelineHandler i get http reason of unauthorized.
I cant seems to figure what is happening in 2012 server - for now i downgrade the mvc4 to .net 4 and change back to server 2008 r2 and everything is working like a clock.
Does anyone got any idea what can be the problem?
thanks.
Related
I have an app service for linux running .NET 5 on Azure, with HTTP 2 set in the configuration section
However, traffic is still getting served using HTTP 1.1. My understanding is SSL is required for HTTP 2, and I am currently using the https://*.azurewebsites.com domain to access it. I think that azure does SSL termination at that point, and my app will get a regular http connection. Could that be why it still gets served using http 1.1? I am using ASP.NET Core, and if I run the site locally it gets served as HTTP 2.
Is there something else that I'm missing?
EDIT:
I enabled/disabled the "Allow client certificates" checkbox on the configuration page, and it started serving it up on HTTP 2. I guess that forced some kind of refresh on Azure's end? It was getting served using http 2 for awhile but is back to http 1.1 now.
UPDATE
Add below code in appsettings.json, then try it.
"Kestrel": {
"EndpointDefaults": {
"Protocols": "Http2"
}
},
Try to use another browser, like chrome or firefox. Or open a new InPrivate window, like below.
Reason: It should be caused by the browser cache. Clearing the cache can also solve the problem.
I got a node.js express application and i need to make it run on my local IIS server so i can send valid http requests to it and work with the responses.
I am using win 10 and IIS 10.
I followed the different guides about working with iisnode in order to use node.js application on IIS.
https://github.com/tjanczuk/iisnode
I also managed to run the tests, so the iisnode is installed, valid and is working together with my IIS.
The "built-in" test is being executed under the default web site which comes with IIS, it creates a new application under it from which there is a working access to the different examples.
My problem is that i am still lacking some information about how to setup my own node.js app on IIS since this information seems to be lacking.
And later on how to overcome issues with invalid http requests.
HTTP status: 500
HTTP subStatus: 1001
HTTP reason: Internal Server Error
I would advice to follow the next guide,
https://harveywilliams.net/blog/installing-iisnode
combined with the official github page of iisnode,
it has all the details about making a simple express node.js app working from scratch with iisnode on IIS.
I would advice to test each part before moving on to the next and once done testing to start first from a minimalistic and simple app of your own and once everything is working build it up from there.
P.S. The reason for this error for me was bad naming when i used express.routing
step 1 :- Install Node js
step 2 :- Install IISNode :- from here
then root folder structure like below.
iisnode folder contains log file and index file.
step 3 :- create angular server side build so it will creates browser and server folder. add them in dist folder as shown in below.
I just installed some nodejs restful app in IIS (Windows server 2008 R2), and seems to be ok. I can access all the get methods using any browser, even from other computers... all these when using the IP address, however, when specifying the URL for that website (example.dev.company), I can only access localy....
My concerns is that when using POSTMAN or SOAPUI to test these methods (even internally), it just waits, and waits till timeout. Any suggestions on what is going on here? I need some other QA members to test these get and post methods using either POSTMAN or SOAPUI...maybe some permissions in IIS, firewall?
thanks in advance
I am trying to host a new ASP.NET 5 WebAPI project in IIS, and I am using the ASP.NET 5 RC 1 runtime. The project that I am using is the standard generated template for a new ASP.NET 5 WebAPI project. (No code changes.)
I have successfully published the project using the command line, and I can get the application to work in a new web site using a specific port, such as localhost:12345. For example, accessing localhost:12345/api/values returns the values.json data from the project template.
However, when I try to use an IIS Application folder for the project, I am getting a 404 error. In other words, localhost:12345/WebApi1/api/values returns a 404 error. But I can see Kestrel running on a random port in the Event Viewer, and if I access the data on that port, I do get values.json back, so I know Kestrel is running.
Is there something special that needs to be done to get an ASP.NET 5 WebAPI project working in an IIS Application folder under a web site?
Side note: if I use --server.urls to set a port for Kestrel, it's running both on the requested port and the random port logged in the Event Viewer. (So it's actually available from Kestrel from 2 URLs, not the single one configured by --server.urls.)
Kiran Challa's link above indeed does fix the problem. Put this in your Configure method in Startup.cs
app.Map("/IISApplicationFolderName", (myAppPath) => this.ConfigureApp(myAppPath, env, loggerFactory));
where IISApplicationFolderName is the name of the IIS application folder that you want to host under. The rest of the configuration code moves to the new method ConfigureApp, since you're delegating your configuration to that method.
This also looks to be a temporary patch until ASP.NET 5 RC2 is released.
I'm working on a signalR project, and was running into HTTP 404 errors when deploying to a server running IIS6 (Windows Server 2003). The 404 was on the signalr/hubs reference. It was suggested in the JabbR chat room to add a wildcard map (* to aspnet_isapi) in IIS to resolve the issue. That did in fact resolve the 404 issue, but I began receiving the error "ASP.NET Ajax client-side framework failed to load".
If I take the wildcard off, the AJAX loads and functions as expected. I have to believe that this mapping is not the correct way to go; perhaps there is a handler that needs registered in the web.config file.
It's worth noting that the entire solution works perfectly on my local (Windows 7) development machine.