Bug#540544: wrong order trying out sources: ~, search, then HTTP

[Mike Hommey]

Hi,

Sorry for the late answer.

On Sat, Aug 08, 2009 at 08:16:17PM +0200, martin f krafft wrote:
> Package: iceweasel
> Version: 3.0.12-1
> Severity: normal
> 
> I have two CNAMEs to a single host on my local network, called flics
> and tunes. Both can be addressed with just the short name, since the
> search domain setup works just fine:
> 
>   piper:~|master|% ping -nc1 tunes
>   PING vizier.oerlikon.madduck.net (192.168.14.5) 56(84) bytes of data.
>   64 bytes from 192.168.14.5: icmp_seq=1 ttl=64 time=0.372 ms
>   piper:~|master|% ping -nc1 flics
>   PING vizier.oerlikon.madduck.net (192.168.14.5) 56(84) bytes of data.
>   64 bytes from 192.168.14.5: icmp_seq=1 ttl=64 time=0.362 ms
> 
> This works analogously for IPv6.
> 
> I also have a directory ~/tunes.
> 
> If I tell iceweasel to open 'flics', it will search Google for 'flics'.
> If I tell iceweasel to open 'tunes', it will give me a view of ~/tunes.
> 
> Both of those are wrong, IMHO. Iceweasel is a browser, *anything*
> entered should *first* be resolved and tried. *Then* — if it must
> — it can look at ~, and only then should it submit to the search
> engine.
> 
> I could not find a way to change this. Thus I am reporting this bug.
> 
> A workaround is http://flics and http://tunes, but that's seven
> characters too many in each case.

Does this still happen with latest releases ? Could you check what kind
of requests it actually tries ?

Cheers,

Mike