As long as we are on this question, I might as well ask a slightly
related one that I would like the answer to without necessarily doing
a bunch of checking of processors -
what are the user-agent headers for various xslt processors when one
uses the document function to GET a resource?
Is the user-agent changed dependent on if the processor is run inside
a browser or not? I know that sounds stupid but I could see that as
the kind of stupid mistake that could creep in.
Actually I wonder if there are any that use # Accept and #
Accept-Encoding in their requests. It seems like a reasonable thing to
put in. Anyone have a good list of tests?
MVH
Bryan Rasmussen
On 8/31/07, M. David Peterson <m(_dot_)david(_at_)xmlhacker(_dot_)com> wrote:
On Fri, 31 Aug 2007 05:26:57 -0600, M. David Peterson
<m(_dot_)david(_at_)xmlhacker(_dot_)com> 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?
Of course re-reading this I think I entirely missed the point of your
question all-together.
Hmmm... Well it certainly isn't the first time. ;-)
--
/M:D
M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |
http://dev.aol.com/blog/3155
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--