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
http://en.wiktionary.org/wiki/ç, 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 . ç
(explain) (anchors) (more from en.wiktionary.org)
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
AOL users can access Wiktionary through this link
after accepting the CACERT certificate. ... Ç, ç.
"tʃə", the fourth letter of the Albanian
en.wiktionary.org/wiki/ç - 15k - Cached - Similar
[ More results from en.wiktionary.org ]
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.
> Components: fetcher
> Reporter: Stefan Groschupf
> Priority: Minor
> Transfered from:
> http://sourceforge.net/tracker/index.php?func=detail&aid=1110243&group_id=59548&atid=491356 > 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:
> and with percent-escaped characters: