<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Trac ticket system susceptible to redirects</title>
	<link>http://spamhuntress.com/2006/09/07/trac-ticket-system-susceptible-to-redirects/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Tue, 02 Dec 2008 15:16:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Christopher Lenz</title>
		<link>http://spamhuntress.com/2006/09/07/trac-ticket-system-susceptible-to-redirects/#comment-38660</link>
		<pubDate>Thu, 07 Sep 2006 15:01:25 +0000</pubDate>
		<guid>http://spamhuntress.com/2006/09/07/trac-ticket-system-susceptible-to-redirects/#comment-38660</guid>
					<description>Trac has an option called "render_unsafe_content" that is disabled by default. If it is disabled, Trac will not render an attachment, but rather add a `Content-Disposition: attachment` header that forces browser to download the file instead of displaying it. That option was added in Trac 0.9.3.

Thus a redirect in an attachment should not be working unless (a) aforementioned option is enabled in the configuration (which is only recommended for closed environments), or (b) it doesn't work correctly in some cases. I have not yet experienced the latter myself, so I think (a) is the issue here, which means it would boil down to a misconfiguration on the lighttpd site and other deployments of Trac.</description>
		<content:encoded><![CDATA[<p>Trac has an option called &#8220;render_unsafe_content&#8221; that is disabled by default. If it is disabled, Trac will not render an attachment, but rather add a `Content-Disposition: attachment` header that forces browser to download the file instead of displaying it. That option was added in Trac 0.9.3.</p>
<p>Thus a redirect in an attachment should not be working unless (a) aforementioned option is enabled in the configuration (which is only recommended for closed environments), or (b) it doesn&#8217;t work correctly in some cases. I have not yet experienced the latter myself, so I think (a) is the issue here, which means it would boil down to a misconfiguration on the lighttpd site and other deployments of Trac.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
