iis

问题 I have an IIS server With a default Website running, an react app running in the the /LandingPage path and an API used by the React app in the /api, so basically I have: localhost:80/ -> Default MVC website localhost:80/LandingPage -> React APP localhost:80/api -> API to be consumed by the APP. Currently I have a domain pointing to the server, so I can access it externally, but I want to create a sub-domain to the APP/API so I don't need to see the /LandingPage in my URL's. Am I able to set

问题 I have an IIS server With a default Website running, an react app running in the the /LandingPage path and an API used by the React app in the /api, so basically I have: localhost:80/ -> Default MVC website localhost:80/LandingPage -> React APP localhost:80/api -> API to be consumed by the APP. Currently I have a domain pointing to the server, so I can access it externally, but I want to create a sub-domain to the APP/API so I don't need to see the /LandingPage in my URL's. Am I able to set

问题 I would like to have all HTTP requests made to my production environment be also automatically made against my testing environment. E.g. if anything makes a request to http://production.site.example.com/api/users/12345 then I want the same request to also be made against http://staging.site.example.com/api/users/12345 by some internal entity that sees the first request. Is there an easy way to set this up in IIS without having to create a custom module or similar? If not, what is the best

问题 I would like to have all HTTP requests made to my production environment be also automatically made against my testing environment. E.g. if anything makes a request to http://production.site.example.com/api/users/12345 then I want the same request to also be made against http://staging.site.example.com/api/users/12345 by some internal entity that sees the first request. Is there an easy way to set this up in IIS without having to create a custom module or similar? If not, what is the best

问题 Our asp.net web application allows our (large) .css and .js files to be cached by client browsers for faster performance. But whenever we deploy a new version, we get phone calls from users about how the page looks messy and is full of javascript errors. It turns out, their browser didn't re-download the changed .css and .js files. Ctrl-F5 always fixes it. Is there any way to force a re-download after upgrade deployments, without setting it not to cache (and thus slowing our application down)

问题 Our asp.net web application allows our (large) .css and .js files to be cached by client browsers for faster performance. But whenever we deploy a new version, we get phone calls from users about how the page looks messy and is full of javascript errors. It turns out, their browser didn't re-download the changed .css and .js files. Ctrl-F5 always fixes it. Is there any way to force a re-download after upgrade deployments, without setting it not to cache (and thus slowing our application down)

问题 when I work in debug with IIS Express in visual studio and try to reach a file in /wwwroot, I don't have any problem with the path = 'wwwroot/fileName'. But when I deploy my website into IIS Express server, I can't reach the file anymore and I get error because the file doesn't exist. Did I make something wrong ? Did the path is not the same when WebSite is deploy ? PS : The file is '.xlsx' extension 回答1: Most likely the file is not being deployed. Assuming you're using Visual Studio, try

问题 I work for a large company with an intranet and Windows AD logins for everyone. We have a number of internal SQL Server databases which allow us to log in using Windows authentication, one of which I'm trying to connect to through an ASP.NET Core application. I can connect to this database through SQL Server Management Studio and query the tables fine. I've followed the tutorial for an ASP.NET Core app using an existing database as closely as I possibly could, and created a single model class

问题 I'm researching a way to integrate a staging environment on our IIS Server, where it is possible to warm up the application before swapping it with the production environment. The only real solution I can find is: Swapping directory settings Which to me sounds like a slow process, because the IIS will have to compile and warmup the new dir after the swap. ( Am I assuming this correctly?) Have two sites, and swap the bindings, after staging has been warmed up. Having a load balancer, and

问题 I am suffering with a web config file that is not rewrite the url for my codeigniter application. here is the web config file. <?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> <rewrite> <rules> <rule name="Clean URL" stopProcessing="true"> <match url=".*" /> <conditions> <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" /> <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" /> </conditions> <action type="Rewrite" url="index.php?{R:1}"