OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: 9.1.10 Construction of the Next Authority URI


Steve and I have discovered an issue with using IIS as an XRI authority server.

It turns out that Microsoft will not let you have a * in the path for "security reasons". 

There is a hotfix that disables URL validation,  but is not recommended.

In our wisdom we thought that we could construct URI like:
http://76.14.26.160/xdiservice-webservice/Default.aspx?localName=
to get around the problem.
This did not work because we are not following the normal append rules for URI construction.
The problem is of corse that in 9.1.10 we are specific about only appending to the path, so we get.
http://76.14.26.160/xdiservice-webservice/Default.aspx/*aaa.3/?localName=
Drummond and I discussed this and decided that a change to line 1460 may be appropriate.
Change:
The final step is to append the Next Authority String to the path component of the Next Authority 

To:

The final step is to append the Next Authority String to the end of the Next Authority 

This would allow authority servers to accept the next subsegment as a path or parameter as they like.

We believe that this is fully backwards compatible with the current authority servers.

I understand that the time to consider this is limited, and apologize for discovering this at the last minute.

I don't see a good reason for the spec to restrict people to only use the path.

Regards
=jbradley


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]