nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Fellows (JIRA)" <>
Subject [jira] Commented: (NUTCH-18) Windows servers include illegal characters in URLs
Date Wed, 26 Apr 2006 21:22:24 GMT
    [ ] 

Chris Fellows commented on NUTCH-18:

Was looking into nutch-18 bug that revolves around
illegal, non-ascii, characters in a url. An example of
a high bit character is 'ç' that maps to a high bit

Before applying any fix, did a brief test with 0.8
trunk. After fetching and indexing onç, I was able to search
on ç and got the following result off the browser

ç - Wiktionary
... Letter [ edit ] Translingual [ edit ] Letter Ç , ç
C with a cedilla ... visit IRC or Wiktionary:AOL . ç
... (cached)
(explain) (anchors) (more from 

So it looks like it will fetch and parse off of urls
with high bit set characters. Additionally, the
display url has the ç encoded correctly as %C3%A7. 

Is this really a bug?

Doing a similar test off of Google on keywords: "ç"
wiktionary. yields:

ç - Wiktionary
AOL users can access Wiktionary through this link
after accepting the CACERT certificate. ... Ç, ç.
"tʃə", the fourth letter of the Albanian
alphabet. ...ç - 15k - Cached - Similar
[ More results from ]

Nearly identical, but the see that the ç is in its
decoded form, not %C3%A7.

I'd say if anything, the bug is that the display urls are in encoded form and not human readable.

> Windows servers include illegal characters in URLs
> --------------------------------------------------
>          Key: NUTCH-18
>          URL:
>      Project: Nutch
>         Type: Bug

>   Components: fetcher
>     Reporter: Stefan Groschupf
>     Priority: Minor

> Transfered from:
> submitted by:
> Ken Meltsner
> While spidering our intranet, I found that IIS may include 
> illegal characters in URLs -- specifically, characters with 
> the high bit set to produce non-English letters. In 
> addition, both Firefox and IE will accept URLs with high-
> bit characters, but Java won't.
> While this may not be Nutch's (or Java's) fault, it would 
> help if high-bit characters (and other illegal characters) 
> in URLs could be escaped (using percent-hex notation) 
> as part of the URL fix-up process, probably right after 
> the hostname lower-case conversion.
> Example document name in Portuguese(with high-bit 
> characters) taken from a longer URL:
> Nota%20tecnica%20-%20Alteração%20de%
> 20escopo.doc
> and with percent-escaped characters:
> Nota%20tecnica%20-%20Altera%e7%e3o%20de%
> 20escopo.doc

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message