<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with apache]]></title><description><![CDATA[A list of topics that have been tagged with apache]]></description><link>https://fusionauth.io/community/forum/tags/apache</link><generator>RSS for Node</generator><lastBuildDate>Tue, 11 Aug 2026 11:22:20 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/apache.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Apache2 reverse proxy setup exposing directory listings and serving unintended files]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/20">@dan</a> The configuration files and logs are inaccessible, assuming you're talking about the ones residing up a directory from /fusionauth-app/.</p>
<p dir="auto">Thank you for stating the risks of the leakage. The only thing that raised flags here was the default fusionauth.properties file in the template directory had the default database user and password, but those should be, and were, changed when installing.</p>
<p dir="auto">I will fork and submit a PR later tonight or this week.</p>
<p dir="auto">Thanks again.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2405/apache2-reverse-proxy-setup-exposing-directory-listings-and-serving-unintended-files</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2405/apache2-reverse-proxy-setup-exposing-directory-listings-and-serving-unintended-files</guid><dc:creator><![CDATA[ctrenner]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>