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 (enclosed in the <system.webServer></system.webServer> section)
First of all -- this really depends on your server configuration -- if such modifications are allowed to be performed on directory level (section is not locked on parent/server level).
In order to disable execution of specific file extension yo need to know the handler name that is responsible for this. On each system this name can be different, especially ...
There are a couple of ways this can be done. IIS7 introduced the integrated pipeline. Many IIS6 developed applications can handle running as is in the IIS7 integrated pipeline, but for the ones that can't there are a couple of options for what can be done. The easiest thing to do would be to switch the app pool the site or application is running to '...
This won't work in an HTML page, so is it possible to configure IIS 7 to have the #include directive work in both HTML and PHP pages? Is there a better way to do this period?
Something that might simplify things for you overall would be to configure IIS to use PHP code inside .html files instead of .php files. Then you'll be able to use PHP code directly in ...
Are you sure you added the correct mime-type to the server? When I test it here locally the iPad seems to be sensitive to which mime-type is used in the response. I've tested it with video/mp4 which seems to work fine but video/mpeg doesn't work.
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
One good and easy way to prevent execution of certain file extensions under an specific folder is to use the "Request filtering" feature of IIS to prevent accessing them altogether.
Go to the folder in IIS and in the "File Name Extensions" tab of the "Request filtering" feature, add "Deny file extension" rules for the file extensions that you want to lock.
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 ...
IIS Server variables
IIS server variables provide information about the server, the connection with the client, and the current request on the connection. IIS server variables are not the same as environment variables.
No. I run several sites like this. The binding determines which app takes the requests, and each app can only have one app pool. An app pool can use multiple processes (a web garden) but that is completely unrelated to wildcard domain names (even a single domain gets split across multiple processes in this scenario).
An app domain (a security construct ...
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 ...
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 ...
You can block favicon.ico requests from the browsers using the rewrite module for IIS.
Basically you must install the module and activate it. Then you must create a rule in your web.config of your site or use the GUI on IIS Admin for creating it.
You can get more info there:
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 ...
I found this can be done with URL ReWrite
Credit to: http://www.youtube.com/watch?feature=player_embedded&v=ut0pD2l4z5c#!
Be sure to add the ServerVariable you choose (HTTP_X_AdminIPAllowed in my example) to allowed server variables from the URL ReWrite module in the IIS Console.
This example allows access to 192.168.1.* clients to ...
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 ...
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 ...
Yes if you allowOverride and then add a new web.config file in the folder you want to disable.
So in your parent folder web.config should look like this.
<location path="." allowOverride="True">
<directoryBrowse enabled="True" />
I've been able to reset a lot of my site's values using appcmd, but I had to dig into specific configurations I wanted to change, which I'll describe a bit below. I know for sure that this works with IIS 7, but I'm not 100% certain whether it passed on to 7.5 so YMMV.
appcmd isn't in my cmd path on any of my installations (though these machines are 2k8sp2) -...
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 '...
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) ...
Sounds like either something is sharing the port or its failing to shut down correctly
Run a netsh http show servicestate to diagnose if anything is running on the HTTP Service.
Additionally do a netstat -ano and see if the IIS service is running on a ID. (I know you said TCPView is reporting ID:0 but this doesn't sound right and I'd put more trust in the ...
It is not the perceived depth of directory that google factors into rankings, urls with so called deep directories can be indexed and ranked just as shorter ones can. http://www.searchenginejournal.com/url-structure-seo/11801/
Though Google does recommend you keep urls as simple as possible. https://support.google.com/webmasters/answer/76329?hl=en
The problem you're having is solved with CORS:
The Cross-Origin Resource Sharing standard works by adding new HTTP
headers that allow servers to describe the set of origins that are
permitted to read that information using a web browser. Additionally,
for HTTP request methods that can cause side-effects on user data (in
particular, for HTTP ...
If all you are doing is moving the files on your file system to another location but want to keep the same URL structure, rather than setting up URL Rewrite rules you can change the physical path of your IIS website configuration.
I will make the following assumptions:
You are running website "mydomain.edu" from a physical location such as C:\inetpub\...
Yes, it will. The http and https version will be seen as individual pages and thus also create duplicate content.
The solution is to use a 301-permanent redirect, which your code does. This will transfer the juice to the destination of the redirection, so you're good. Also, adding a canonical tag to indicate which is the prefered url is good practice.
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.
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 ...