I just wrote a description on how you can use apache to create an authenticated proxy ahead of your development server, or other http-based servers that doesn’t provide authentication themselves.
You can find it under the docs-section or by clicking here: Using apache to create an authenticated proxy.
Jeg har visst om at disse ville komme en stund, de nye nettsidene har vært tilgjengelig som beta en stund, i ekte web-2.0 stil.
De nye nettsidene har nå erstattet de vanlige nettsidenepå uib.no, og har et tiltalende visuellt preg. Den viktigste nyheten er IMHO “Det skjer”-kalenderen. Nå har det blitt enkelt å få vite om gjesteforelesninger og slikt, som for eksempel foredraget til Richard Stallman “The Free Software Movement and the GNU/LINUX Operating System” 19. februar klokken 17:00.
PS: de nye nettsidene er Zope (Python)-drevet 
I installed Ubuntu 8.04 this week. Among the new features are a beta of the coming release of Firefox. It seems like some fine peace of software, but it continues the ever-growing wasting of screen realestate. I bought a new laptop a few weeks ago, and I wanted a small and portable one. In order to get that, I had to go down to a screen resolution of 1024×768. I was a bit afraid that this would be too little, but it has turned out fine. But it irritates me that some developer seems to think that it is no problem at all to use up a large portion of the screen for toolbars.
When I started using phoenix (the name of firefox at that time), one of its selling points was that it left so much of the screen for webpages, and didn’t waste much space at all. With every new (standard) theme it seems like it eats more and more of the screen.
And, since this is a beta none of my beloved “screen realestate cheap”-themes are out for it yet.
F11 and out.
Today I noticed this in my access.log:
67.19.113.154 - - [24/Mar/2008:16:02:10 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 363 "-" "-"
65.111.181.35 - - [24/Mar/2008:20:02:22 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 363 "-" "-"
67.19.113.154 - - [24/Mar/2008:20:15:38 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 363 "-" "-"
67.19.113.154 - - [25/Mar/2008:00:26:37 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 363 "-" "-"
67.19.113.154 - - [25/Mar/2008:04:37:39 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 363 "-" "-"
...
67.19.113.154 - - [25/Mar/2008:08:52:25 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 363 "-" "-"
67.19.113.154 - - [25/Mar/2008:13:05:07 +0100] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 363 "-" "-" |
What goes on here?
All these requests fail, ofcourse, but in addition to the obvious (404), the client also doesnt supply a Host: header for their HTTP/1.1 requests
update
It is safe to assume that this is an attempt to hack me in some way, DFind is appearantly some kind of security scannerref. The same IPs are also bruteforcing some URLs (like /phpmyadmin etc..) looking for somthing fun to poke around with.
Save on delicious
