[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
On Fri, 31 Aug 2007 04:29:46 -0600, Elliotte Harold <elharo@xxxxxxxxxxxxxxx> wrote:
Saxon as well as Saxon on .NET provides the ability to use a credential cache that is associated with an XmlUrlResolver (XmlUrlResolver.Credentials[1] as it relates to Saxon on .NET. Can't remember exactly the equivalent class for Java) and when accessing an external document that requires authentication will locate the specified URI in the credental cache of the XmlUrlResolver and use the specified credentials transparent to the in-process transformation file.
Of course the same is true about System.Xml.Xsl, though the day Elliotte Rusty Harold first embraces to then switch his focus to the .NET platform will be on or about the same day Microsoft not only opens the source of Windows and Office, but does so under the GPLv3. ;-)
Of course you can also write a custom URI resolver, but my guess is that,
1) You obviously already knew this, and
2) Your obviously after out of the box solutions, and so therefore
3) The above three lines as well as this one are a complete waste of time and space. ;-)
[1] http://msdn2.microsoft.com/en-us/library/system.xml.xmlurlresolver.credentials(VS.71).aspx
M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 | http://dev.aol.com/blog/3155
Re: [xsl] HTTP authentication support
Subject: Re: [xsl] HTTP authentication support From: "M. David Peterson" <m.david@xxxxxxxxxxxxx> Date: Fri, 31 Aug 2007 05:26:57 -0600 |
On Fri, 31 Aug 2007 04:29:46 -0600, Elliotte Harold <elharo@xxxxxxxxxxxxxxx> wrote:
Which, if any, processors support HTTP authentication in the URLs they retrieve? Both for the initial document and documents retrieved by the document() function?
Saxon as well as Saxon on .NET provides the ability to use a credential cache that is associated with an XmlUrlResolver (XmlUrlResolver.Credentials[1] as it relates to Saxon on .NET. Can't remember exactly the equivalent class for Java) and when accessing an external document that requires authentication will locate the specified URI in the credental cache of the XmlUrlResolver and use the specified credentials transparent to the in-process transformation file.
Of course the same is true about System.Xml.Xsl, though the day Elliotte Rusty Harold first embraces to then switch his focus to the .NET platform will be on or about the same day Microsoft not only opens the source of Windows and Office, but does so under the GPLv3. ;-)
Of course you can also write a custom URI resolver, but my guess is that,
1) You obviously already knew this, and
2) Your obviously after out of the box solutions, and so therefore
3) The above three lines as well as this one are a complete waste of time and space. ;-)
[1] http://msdn2.microsoft.com/en-us/library/system.xml.xmlurlresolver.credentials(VS.71).aspx
-- /M:D
M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 | http://dev.aol.com/blog/3155
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] HTTP authentication suppo, Colin Paul Adams | Thread | Re: [xsl] HTTP authentication suppo, M. David Peterson |
Re: [xsl] HTTP authentication suppo, Colin Paul Adams | Date | Re: [xsl] HTTP authentication suppo, M. David Peterson |
Month |