On Wed, Oct 26, 2016 at 09:58:57AM +0200, Yann Ylavic wrote:
> On Tue, Oct 25, 2016 at 9:48 PM, Petr Gajdos wrote:
> >
> > So if I understand correctly, content of mime.types is hardcoded.
> > Is there another chance than patching either TestConfig.pm or
> > extra.conf.in to contain application/xm
On Tue, Oct 25, 2016 at 9:48 PM, Petr Gajdos wrote:
>
> So if I understand correctly, content of mime.types is hardcoded.
> Is there another chance than patching either TestConfig.pm or
> extra.conf.in to contain application/xml .xml definition?
Don't you have a piece of conf that applies to your
> On Wed, Sep 21, 2016 at 08:38:25PM +0200, Yann Ylavic wrote:
> > Without any AddType directive relative to ".xml" files in your
> > configuration, the Content-Type is set according to the
> > "conf/mimes.types" file.
> > What's in yours for the "xml" extension?
>
> You are correct. There is no r
On Wed, Sep 21, 2016 at 08:38:25PM +0200, Yann Ylavic wrote:
> Without any AddType directive relative to ".xml" files in your
> configuration, the Content-Type is set according to the
> "conf/mimes.types" file.
> What's in yours for the "xml" extension?
You are correct. There is no reference to xm
On Wed, Sep 21, 2016 at 11:04 AM, Petr Gajdos wrote:
>
> the test does not succed for me. If I got it correctly, it creates
> test.xml with the content 'helloworld' and tries to add CASEFILTER to
> it trough AddOutputFilterByType with application/xml. That does not
> work for me, but does with tex
Hi list,
the test does not succed for me. If I got it correctly, it creates
test.xml with the content 'helloworld' and tries to add CASEFILTER to
it trough AddOutputFilterByType with application/xml. That does not
work for me, but does with text/xml as example [1] shows.
Where the truth is?
Petr
