Hot answers tagged

7

It is not recommended to cache resources with a query string. A query string usually represents a dynamic resource. However IE and Chrome do cache based off the Cache-Control and Expires headers. Firefox should cache, however, this could be due to a weak validation i.e. no usage of Etag. Using Etag forces strong validation of the cache-control mechanism ...


5

First off, 128-bit AES is very good. The prevailing opinion is that it is secure for the future close enough to care about. Setting that aside, the reason you're getting 128-bit encryption is because that was what was negotiated. The certificate has little to do with it; the SSL cert is an RSA keypair, and there's no way that's only 128 bits. It's more ...


5

After much research, I found this article on the Comcast forums: http://forums.comcast.com/t5/Home-Networking-Router-WiFi/SMCD3G-Can-t-access-web-server-from-LAN-from-Internet-OK/m-p/1754823#M55009 Essentially, certain models of Comcast routers (both home and business class) will experience an "issue" where requests made from inside the network "die" at the ...


5

There are two main approaches to figuring this type of thing out. Either determine what is the common factor shared by the affected users, or what changed recently so that these users are suddenly affected. Your best bet is to approach it from both directions, as the answer ends up being a mixture of both. What Ties These Users Together? If they don't have ...


5

I'm very surprised that Google is indexing the HTTPS pages with a broken certificate. Google usually prefers the HTTPS site if they both work, but I've never seen it prefer HTTPS when there is a broken cert. Another solution would be to implement rel canonical link tags that point to the HTTP version. Every page on your site should have a tag pointing to ...


4

The AddType directive lets you specify what MIME type(not entirely a complete list) a given file extension should be processed as. To make an arbitrary extension be processed as HTML: AddType text/html .whatever Note that there's generally very little reason to do this sort of thing, and it mostly just introduces maintenance work.


4

The only real advantage of increasing the number of worker processes is if you've got some long running process that's blocking the other threads from running - in which case you might want to consider adding another Worker Process. However, as you've found this basically spools up another instance of w3wp.exe with it's own memory space that doesn't share ...


4

Your robots.txt file does not appear to conform to the robots.txt specification (you must specify the user agent before the directives and I do not believe that Noindex is a valid directive). Consider the following updates: User-agent: googlebot Disallow: /Office/LocationDetails.aspx Disallow: /office/default.aspx Disallow: /Electronics/Communitylist.aspx ...


4

Use RewriteLog and RewriteLogLevel directives to log such activity (IIS restart most likely will be required). The higher value you put for RewriteLogLevel the more verbose/detailed it will be. If your site is busy (has lots of requests) then you will have hard times debugging it (log will become huge in a matter of seconds/minutes and it will become ...


4

Are all requests from those users slow or only some of them? Does it happen to them on all browsers? Can you write a test program, that does the same queries without a browser? Is anti-virus enabled? Firefox has safebrowsing, which first queries google if the pages you want to visit are safe. Best thing you can get is a full trace with wireshark, so you can ...


3

It became known in 2009 that IIS had a vulnerability in that it determined filetype by the part of the filename preceeding a semicolon if there was one in the name. See this NIST description for more details.


3

No, you don't need to specify a DNS server on your PC, but you need to register a dynamic DNS entry for your domain, that points to the IP of your PC/network. Please remember that most internet service provider do have private and commerial contracts, where the upload speed for private internet connections it limited in most cases. Most providers even ...


3

Have a look a godaddy's support article on nameservers (though this isn't clear on what you're supposed to do with domains registered with them and hosted with them). The information they have given you isn't correct, pinging ns1.asezo.com returns nothing, so there isn't a nameserver there. I would suggest calling support back.


3

I think you have to enable https in IIS itself. The following links will help http://support.microsoft.com/?id=324069 http://support.microsoft.com/?id=298805


3

Using an SSL certificate will encrypt the communication between client browsers and your website. Depending on how serious your client is about security, two questions that you might want to further consider for downloads are: 1). Can a hacker replace download files with deleterious ones? If the files are added to your site via FTP or share a common ...


3

There are two solutions I can think of: Find patterns in the redirects and see if you can cut the number down. For example, if you had a large chunk that redirected from one folder to another, you could match something like /folder/([A-Za-z0-9-]+) and redirect to /newfolder/$1. This might still leave a large number of redirects though. Redirect all unfound ...


3

You should set three A records poiting to your server IP. *.mydomains.com www.mydomain.com blog.mydomain.com Then you need to set up your Virtual Host correctly to accept requests for all three domains/subdomains (see e.g. Virtual hosting with IIS (Internet Information Services) or Setting Host Headers in IIS 6.0). Redirect needed domains to one desired ...


3

When I set up the DNS servers I am getting example.com is working to the site, but www.example.com isn't and is showing a 404 error. Since you're receiving a 404 error code from a server, that likely means your DNS is configured properly, but your web server is not redirecting to the same content that your non-www (root domain) is returning. Assuming that ...


3

Since the rule is only rewriting the URL, it should return a standard '200' HTTP header code (assuming there are no other errors). If you had used a redirect action type instead of rewrite, then you would have received a 301 or 302 HTTP response code depending on how the rule was configured. There are a variety of tools available that you can install on ...


3

This was solved by removing managed code in the application pool. Change the .NET framework version for the application pool for the remote proxy site to 'no managed code' It's obvious in hindsight!


3

You are not using routable domain names. You are using NetBios names which are only routable on Microsoft networks. The Internet does not know what gisedn is. For you to access your website external to work, you need a domain name (example.com), a static IP address or a way of using dynamic DNS (DDNS), the ability to route these requests through the firewall,...


3

I don't think you'd see any direct SEO impact however provided your primary domain is working correctly, other than the fact that more people landing on error pages means less visitors reaching your website. Depending on your hosting setup you may be able to ensure that the redirect still works with an HTTP 301 response without the SSL protocol - you'll ...


3

In IIS Settings the option Require SSL/TLS must be turned off. With it turned on, HTTP will always return a 403.4 Forbidden error. With it turned off, the Permanent SEO-safe 301 redirect from HTTP to HTTPS option works, automatically rewriting the http address into a https address.


3

The reverse proxy should be entirely invisible to the user, so no, it should not in any way affect SEO. If, however, the (remote) server you were proxying to was slow or on a slow connection then yes, that could affect SEO, simply because it would slow everything down. But that does not seem to be the case here.


2

Add an A NAME record of * and then your ip address of your hosted server to your DNS settings of your domain name.


2

From https://stackoverflow.com/questions/117931 Use the following rewrite rule to forward the entire URL into your script: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php?q=$1 [L,QSA] Then inside your index.php script, get the 'q' parameter, and split it on slashes. Put the values into a map. $pathmap = ...


2

Although I'm a bit late to the party, I would like to suggest this syntax, which is a bit shorter (and IMHO cleaner) than the accepted one: <rule name="Redirect to HTTPS except /nossl/ folder" enabled="true" stopProcessing="true"> <match url="(.*)" /> <conditions logicalGrouping="MatchAll" trackAllCaptures="false"> <add ...


2

Scott Forsyth - MVP's answer to 'Different file locations for http v https on IIS?' suggests that you look at Failed Request Tracing to help identify the fault, I'd also suggest checking the IIS logs to see exactly what is happening to the request for default.aspx, it must be going somewhere!


2

According to this knowledge base article, MatrixStats is owned by FastHosts.co.uk and is available only to their customers. You could use Google Analytics, or try one of the following programs: IIS Log Analyzer Weblog Expert Easy AWstats for IIS instructions


Only top voted, non community-wiki answers of a minimum length are eligible