atom feed11 messages in ru.sysoev.nginxRe: Using XSLT and FastCGI together
FromSent OnAttachments
Michael NachbaurApr 15, 2009 10:09 am 
Michael ShadleApr 15, 2009 10:29 am 
Igor SysoevApr 15, 2009 11:17 am 
Igor SysoevApr 15, 2009 11:17 am 
Michael NachbaurApr 15, 2009 11:23 am 
Maxim DouninApr 15, 2009 11:26 am 
Michael NachbaurApr 15, 2009 12:25 pm 
Igor SysoevApr 17, 2009 11:21 am 
Michael NachbaurApr 19, 2009 7:54 am 
Igor SysoevMay 11, 2009 11:04 pm 
Michael NachbaurMay 12, 2009 12:36 pm 
Subject:Re: Using XSLT and FastCGI together
From:Igor Sysoev (is@rambler-co.ru)
Date:Apr 15, 2009 11:17:12 am
List:ru.sysoev.nginx

On Wed, Apr 15, 2009 at 10:10:07AM -0700, Michael Nachbaur wrote:

I'm developing a web application that makes heavy use of nginx's XSLT support (Thank you for that!) About half of the content is in static XML files that describes the application's state. But when people click on and interact with the forms and links on the page, those make calls to URLs which get dispatched to fastcgi daemons using fastcgi_pass.

What I'd like to do is output XML from my FastCGI daemon and feed that through nginx's XSLT stylesheets in order to render the dynamically- generated page. But I'm finding that even though my fastcgi_pass directive lives in the same location block where my xslt is defined, nginx is sending the raw XML to the browser.

Is there a way to tell nginx to process the output of my FastCGI script with XSLT?

By default nginx processes only "text/xml" with XSLT. Probably you send some different type. You may add it in xslt_types.