Package: urlscan Version: 0.5.5 Severity: normal Trying to surf to the URL http://www.faz.net/m/{88B0CAF6-DE67-4F88-9E93-8EFDD99EBCF3}File2.jpg I notice how urlscan trims the URL after /m/ -- it probably doesn't see {} as being a valid URL character. I am not sure whether they are, nor can I be bothered to check the RFC because they are in use and they work with browsers. Could urlscan thus please also honour them?
Another URL I had problems with was one using unescaped @ signs, like this: http://server/path/to/cgi?a=b&[EMAIL PROTECTED] Again, this is probably not RFC-compliant, but it works and it would thus be nice if urlscan honoured it. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (750, 'unstable'), (500, 'testing'), (250, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages urlscan depends on: ii python 2.4.4-2 An interactive high-level object-o ii python-central 0.5.12 register and build utility for Pyt ii python-urwid 0.9.7.1-1 curses-based UI/widget library for urlscan recommends no packages. -- no debconf information -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
