Migrating to a new server and thought I'd take the time to set up a
cookieless subdomain on it for static files.
In my current setup, 403 errors are sent to a php file which grabs the
$_SERVER["REQUEST_URI"], locates the page of the photo on the site, and
redirects the person to that page so they
As mentioned before, I'm tweaking pixabay's version of handling the new
Google Image search traffic killer by making their trap URLs more
cacheable.
Img tags in the html will have ?i appended to the source and those "?i"
are removed for bots. I thought I could use nginx's httpsubmodule to strip
th
On Mon, April 15, 2013 1:49 pm, Francis Daly wrote:
> On the nginx side, there should be approximately nothing special to do.
>
> The nginx.conf that works on your production server can be put onto your
> development server; "listen" directives which specify ip addresses may
> need to be changed, a
As I'm about to launch some major additions to my site (and launch another
site) I've been starting to get my act together in regards to development,
e.g. finally starting to use git, getting ready for a responsive redesign,
etc.
I've realized that it would probably be wise to develop locally by r
I began thinking about using Puppet to automate deployment and that led me
to thinking about using rpms to make keeping up with new releases easier.
Since I've always compiled nginx from source, I was curious how one
specifies configure arguments like --with-http_ssl_module and
--with-http_gzip_s
Just curious...
In a lot of examples I've seen on the net for setting up fastcgi-cache the
directives
fastcgi_ignore_headers Cache-Control Expires;
expires epoch;
are included. Is there any major reason for that? For my own setup I want
the fastcgi caching to reduce load on the server, but I'd a
On Fri, February 22, 2013 5:51 am, Namson Mon wrote:
> Hi Ian, we've just published an extensive blog post about how to achieve
> this kind of hotlinking protection against Google Images:
just curious...unless I missed it in the article...how are you adding the
GET param for visitors, but not for
If I understand correctly, nginx doesn't do multiple conditions in an 'if'
or nested if's.
Based on some of the ideas being tossed around in this thread
(http://www.webmasterworld.com/google/4537063-11-30.htm) I'd like to
rewrite serve up a one pixel gif to whenever both of the two following
condi
