Hot answers tagged iis7
8
There are a few ways you can do this but if you have the URL Rewrite Module installed, it's fairly easy and a good way to do it.
You can paste the below configuration into your site's web.config file.
<rewrite>
<rules>
<rule name="https redirect">
<match url="(.*)" ignoreCase="false" />
...
7
IIS7+ is actually pretty darn' fast. There isn't much you can do to speed up IIS; in general you'll optimize on the HTML, JS, Images, CSS, HTTP, HTTP headers, and possibly webapp code (C# etc). These issues are cross-platform. The user interface is of course different between Apache and IIS, but the knowledge is much the same.
Steve Souders literally wrote ...
6
It is definitely System Log.
Which Log file? Well -- you can check the physical path by right clicking on the System Log (e.g. Server Manager | Diagnostics | Event Viewer | Windows Logs). The default physical path is %SystemRoot%\System32\Winevt\Logs\System.evtx.
You can create a Custom Filter and filter by "Source: WAS" to quickly see only entries ...
6
There's nothing explicitly wrong with it. It's just a domain. It's as cumbersome as you choose to make it. Some legitimate concerns, however, would revolve around the testing of security and certificates, etc.
Since certificates are based on the TLD, it would be impossble to run tests against any web service that sits behind an SSL layer.
Similarly, ...
5
In order for IIS to allow access to the file at all, it needs to be assigned a MIME-type. Use application/octet-stream and the browser will almost certainly treat it as a file it can't handle itself.
(You could also experiment with application/x-whatever-you-want)
4
From How to change the TCP port for IIS services
Open Internet Information Services (IIS) Manager.
Select the Web site that you wish to configure.
In the Action pane, click Bindings.
Click Add to add a new site binding, or click Edit to change an existing binding.
Click OK to apply the changes.
3
This can be done with URL Rewrite module using "Reverse Proxy" kind of rule (when incoming request is handled/internally redirected to be processed by another back-end server), but for this you will also need an Application Request Routing to be installed. Unfortunately I have not dealt with AAR much and cannot really advise further. With Apache it is easier ...
3
There are lots of bots (computer programs) that visit webpages. However, they pretend to be real users by using the user agent of a popular browser, such as IE or firefox or chrome; instead of using their own specialized user agent so the server knows they aren't real people. As a result, the IIS logs count them as real users. Google Analytics doesn't, ...
3
If your environnement is identical, i mean with the same physical path, ip etc.. you can just applicationHost.config.
The file is by default located in the C:\Windows\System32\inetsrv\config it's an xml file, si if you rigth a little tool you could change your binding before restore the file in your dev environnement
3
From memory (I had to research this a few years ago) it has to do with what ISAPI extension is handling the redirect - what you want is something which is running in the same process space as IIS otherwise the redirection can actually slow or choke the webserver depending on the volume.
I believe that the method you describe above is performing the rewrite ...
3
It's really very hard to suggest anything without more information, the nameserver thing is weird but not unheard of in the messy world of DNS. If I had to guess I'd say it's something local rather than your site.
The most common cause I've seen for this kind of thing is the adblock plugin, cached DNS information or overactive antivirus/antimalware. I'd ...
3
Windows Authentication will really only work if the IIS server is joined to the domain. That's the first thing you'll want to do (assuming you can). Once you do - WindowsAuthentication will make authentication a breeze. If joining the domain is out of the question, then you'll at best be able to use a mechanism based on forms authentication that could ...
3
At its root, this is almost certainly a database problem. The first thing to check is the indexes on the tables. If the full-text search is fast and the SELECT is slow, then there are most likely JOINS being performed that could benefit from indexes, possibly even composite indexes.
You will need to profile the application (run a trace using SQL Profiler) ...
2
Have you tried setting the following?
<system.webServer>
<httpErrors existingResponse="PassThrough" />
</system.webServer>
Here are a couple of references on error pages:
http://www.iis.net/ConfigReference/system.webServer/httpErrors
http://blogs.iis.net/ksingla/archive/2008/02/18/what-to-expect-from-iis7-custom-error-module.aspx
2
In answer to your question:
1 . My server has a distinct IP, can I use it although I have other sites
there but they don't need ssl?
There is really no mucking about when it comes to SSL, your site will need its own IP address for a single domain SSL. There are various hacks and bodges I've seen people do over the years, they all end in tears.
2 ...
2
I don't necessarily agree that a domain always has to be short. It depends a lot of how it is used. Let's say you're an agency having to show multiple projects to multiple customers, but not all these customers actually do have domains of their own, so something like supercooldemo.customer.com will not always be possible.
So, you'll probably end up with ...
2
What you should look into whether or not there is an issue with the "byte range" HTTP requests feature of IIS7. Any issue with that would cause the byte_range_error_message error.
For example, here's an IIS 7.5 hotfix for byte range requests that was causing problems with streaming PDFs: http://kb2.adobe.com/cps/807/cpsid_80780.html
Since IIS7 typically ...
2
What is the request URI for the CSS file? Firefox will not cache the result when the URI contains a query string (i.e. a ? followed by parameters).
According to the HTTP specifications, a browser should never cache a response from a request containing a query string unless the server explicitly allows it. Unfortunately though, Firefox and IE do not comply ...
2
This may be a problem if there is a server in between which is decompressing the content, such as a load-balancer, CDN, or proxy. If the content is sent encrypted on localhost, it will be sent encrypted to you unless there is a client in between which does not have the Accept-Encoding:gzip header in the request.
The best way to check for compression is to ...
2
All that you have done in that code is enable PHP on the server. You need to either rewrite or redirect your .html pages to the corresponding .php pages with the IIS URL Rewriter.
Something like this might work for you. Put it in system.webServer.
<rewrite>
<rules>
<rule name="REWRITE_TO_PHP">
<match ...
2
You haven't specified a web server however you appear to be involved in .net so I'm going to assume it's IIS
In which case you can filter your logs using something like this http://learn.iis.net/page.aspx/692/advanced-logging-for-iis---log-filtering/
You can do the same on most servers
You can't actually stop browsers requesting the image.
However if you ...
2
The applicationHost.config is not necessary in this case since you're going to setup a development server.
I would copy over the configuration to your dev box. The easiest way to do this is to go into IIS on your production server, click on the root server and select Shared Configuration.
Then click Export Configuration... and select a location.
Then on ...
2
Yes, you should 301 redirect /category.aspx?id=widgets to /category/widgets/ so that there is only a single URL that resolves the page.
Make sure that you don't accidentally create a redirect loop.
The alternate way is to use the rel="canonical" meta-tag in your code, but as you are using IIS7 the redirect should be simpler to implement.
2
Regardless of SEO, I suspect that would be confusing to users. If they are expecting to see one website and then see another without an explanation what would they think? Wouldn't an explanatory message that the site is down for maintenance with a link to the other site be not only more transparent for users, but good for search engines as well?
2
If there's an actual need to maintain the original website, you can use IIS's rewrite module to rewrite the URLs, or if they have to be hosted on separate servers, IIS's rewrite module can also be set up as a reverse proxy.
Though generally the simpler the setup the better. If you can use paulmorriss' solution and just set up the public domains with ...
2
<configuration>
<system.webServer>
<httpRedirect enabled="true" exactDestination="true" httpResponseStatus="Found">
<add wildcard="*.php" destination="/default.htm" />
</httpRedirect>
</system.webServer>
</configuration>
2
The easist way to solve this is version the name of your CSS file e.g. style-v1.css, increment the number when you make major changes and you'll never have this problem again.
Having far future expiration dates on your images and media helps your users as they don't download the same files over and over again while browsing your site. Both expiration dates ...
Only top voted, non community-wiki answers of a minimum length are eligible
