Re: Working with svnindex.xsl

Hi,

As an addendum to this thread ... when we deployed the
SVNIndexXSLTparameter to our Apache config we ran into problems with our
internal Google appliance scanning of the Subversion repositories.

This was because Google did not understand the XML being presented and was
not capable of downloading and parsing the XSLT style translation.

I thought it would somehow be possible to detect the User-Agent being
reported by the client and return the XSLT page only for browsers which
were capable of understanding it (Firefox, Mozilla, Internet Explorer,
etc).

I found documentation at
http://gentoo-wiki.com/HOWTO_Apache2_with_subversion_SVN_and_DAV#Pretty_formatting
talking about a similar problem with Opera being unable to parse the XML.

Their solution was to use xsltproc to pre-process the produced XML and
produce HTML content for browsers which don't understand XSLT XML headers.

BrowserMatch "Opera" xsltfilter

ExtFilterDefine xslt mode=output enableenv=xsltfilter \
        intype=text/xml outtype=text/html \
        cmd="/usr/bin/xsltproc /path/to/svnindex.xsl -"

Then within the <Location> section defining the Subversion repositories
add an output filter:

SetOutputFilter xslt
AddDefaultCharset utf-8

Cheers,
Dg.

--
David Grierson
JPMorgan - IB Architecture - Source Code Management Consultant
GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson_at_jpmorgan.com
Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
 
Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s).  All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org