[jira] Resolved: (ABDERA-218) IRI.toString() doesn't preserve empty fragment identifiers and queries

["James M Snell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ABDERA-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James M Snell resolved ABDERA-218.
----------------------------------

    Resolution: Fixed

Checked in

> IRI.toString() doesn't preserve empty fragment identifiers and queries
> ----------------------------------------------------------------------
>
>                 Key: ABDERA-218
>                 URL: https://issues.apache.org/jira/browse/ABDERA-218
>             Project: Abdera
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Niklas Lindström
>            Assignee: James M Snell
>
> Calling toString() on IRI objects doesn't preserve empty fragment identifiers and queries. According to RFC 3987 (from 3986), they should.
> The following two examples fail:
>     IRI iri = new IRI("http://example.org/foo#");
>     assertEquals(iri.toString(), "http://example.org/foo#");
>     iri = new IRI("http://example.org/foo?");
>     assertEquals(iri.toString(), "http://example.org/foo?");
> Also note the bullet in at RFC 4287, 4.2.6 <http://tools.ietf.org/html/rfc4287#section-4.2.6> which says "Preserve empty fragment identifiers and queries.".
> (This should be fixed by changing the relevant bits in IRI.buildSchemeSpecificPart to:
>       if (query != null)) { ...
>       if (fragment != null)) { ...
> .)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.