W3C home > Mailing lists > Public > www-validator-cvs@w3.org > May 2009

[Bug 6915] New: Encoded unicode chars errors as "broken URI fragments"

From: <bugzilla@wiggum.w3.org>
Date: Mon, 18 May 2009 14:19:51 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-6915-169@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6915

           Summary: Encoded unicode chars errors as "broken URI fragments"
           Product: LinkChecker
           Version: 4.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: checklink
        AssignedTo: ville.skytta@iki.fi
        ReportedBy: boujin@yahoo.com
         QAContact: www-validator-cvs@w3.org


Encoded unicode chars in a link anchor are incorrectly described as "broken URI
fragments". (It seems the program does not recognize encoded chars in an
anchor.)

Example:
http://www.domain.org/folder/file#espa%C3%B1a



Error output:
=============================================================================
    Status: 200 OK

    Some of the links to this resource point to broken URI fragments (such as
index.html#fragment). 
=============================================================================



But encoded unicode chars in other parts of the url do not output error.
Example:
http://www.domain.org/espa%C3%B1a/espa%C3%B1a



P.S.
I am using http://validator.w3.org/checklink which currently is version 4.5.
Unfortunately, only version 4.4 is available at the bug report drop down menu.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 18 May 2009 14:20:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:35 UTC