I'm using drakma to GET data over http. It turns out that when following redirects, drakma uses the location in the redirection header, which it url-encodes. Usually this might not be a problem, but when the location redirected to is already url-encoded this method fails. Is this intended behaviour? I'm not sure what the clean solution to this would be, as decoding the location before using it just doesn't feel right. For the lack of a better solution that's what i'm doing right now though. Any pointers in the right direction would be greatly appreciated. Best regards, Wilfried Nesensohn