Accessing a HostGator SVN repository via SVN+SSH on Windows This information should be helpful to anyone trying to access an svn repository stored on a remote (shared) server which does not expose an svn server. My host is HostGator (good speeds, reliable ssh, cgi-only, MyISAM-only, decent support, non-existent knowledgebase). HostGator runs SSH over port 2222… Read More Accessing a HostGator SVN repository via SVN+SSH on Windows
Over the past two months, we’ve received significant community feedback that using a new attribute on the Content-Type header would create a deployment headache for server operators. To that end, we have converted this option into a full-fledged HTTP response header. Sending the new X-Content-Type-Options response header with the value nosniff will prevent Internet Explorer from MIME-sniffing a response away from the declared content-type.
For example, given the following HTTP-response:
HTTP/1.1 200 OK
Date: Thu, 26 Jun 2008 22:06:28 GMT
This page renders as HTML source code (text) in IE8.
To change the configuration for php running as cgi those handy module commands won’t work.. The work-around is being able to tell php to start with a custom php.ini file.. configured the way you want.
I just made some fixes to the mirrors I run at:
This is the .htaccess file that I came up with, note I painstakingly
determined the languages.. (In the future it would be great to get each
corresponding charset for the AddCharset directive)… Read More Multi-Language and Content-Negotiation for Mirror
Users will be authenticated if squid is configured to use proxy_auth ACLs.
Browsers send the user’s authentication credentials in the Authorization request header.
If Squid gets a request and the http_access rule list gets to a proxy_auth ACL, Squid looks for the Authorization header. If the header is present, Squid decodes it and extracts a username and password.
If the header is missing, Squid returns an HTTP reply with status 407 (Proxy Authentication Required). The user agent (browser) receives the 407 reply and then prompts the user to enter a name and password. The name and password are encoded, and sent in the Authorization header for subsequent requests to the proxy. Also see this example Authorization Header from .htaccess files.
NOTE: The name and password are encoded using “base64” (See section 11.1 of RFC 2616). However, base64 is a binary-to-text encoding only, it does NOT encrypt the information it encodes. This means that the username and password are essentially “cleartext” between the browser and the proxy. Therefore, you probably should not use the same username and password that you would use for your account login.