Tori returns
04 Jan 2006Finally, something non-geeky worth posting about! :D (Even though I took a crap photo :P Meh :P)
Welcome back wonderful!
I’ve delivered simple, clear and easy-to-use services for 20 years, for startups, scaleups and government. I write about the nerdy bits here.
— @joahua
Finally, something non-geeky worth posting about! :D (Even though I took a crap photo :P Meh :P)
Welcome back wonderful!
This is a rather bizarre problem affecting Firefox 1.0.x on Mac OS X and Windows, but not Linux. Even IE escapes unscathed (well, as unscathed as it ever does when using PNG graphics. That is to say, relatively fine when using filter: properties).
Load up this post in Firefox 1.0.x (not on Linux) and note the difference between the two graphics above. There is a 1-pixel yellow horizontal line along the bottom of the first image (generated by Photoshop). The second image — near identical — should not bear any such mark.
The 1-pixel transparency (yellow is a background colour set using CSS) is not in the source file in Photoshop, and does not display in any other browser, including Firefox 1.5/Flock. The GIMP version was made by opening the graphic, smudging an all-white area (i.e. white-to-white, so it recognised the file had changed but was visually identical), and re-saving.
On a hunch that Photoshop was a horrible, horrible monster. I was right!
So, my question to the world: did I do something wrong in Photoshop? Has anyone seen this behaviour before? What’s going on?!
*goes slowly insane*
I don’t know why. Shrug.
I had to setup a virtual host that proxied through to another server today, and found the Apache 2.0 documentation on that matter particularly unhelpful for a rather trivial reason.
Here’s their broken version:
<VirtualHost *:*> ProxyPreserveHost On ProxyPass / http://192.168.111.2 ProxyPassReverse / http://192.168.111.2/ ServerName hostname.example.com </VirtualHost>
Here’s my working version:
<VirtualHost *:*> ProxyPreserveHost On ProxyPass / http://192.168.111.2/ ProxyPassReverse / http://192.168.111.2/ ServerName hostname.example.com </VirtualHost>
Spot the difference.
Yes, it was as simple as an omitted trailing slash.
Only takes a minute or two to figure out what’s going wrong, but it’s pretty darn annoying for that minute: I assume, as would many people, that documentation is generally infallible — its purpose being the cure to various software ailments, not the cause! Ah well. I’d have edited the Apache documentation, but it’s not a wiki and I can’t be bothered joining whatever mailing list I’d have to join to get one character added to their site!