<?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[Request: Support for HTML5 History]]></title><description><![CDATA[<p dir="auto">I’ve noticed that using dynamic routes on a static Vue SPA poses a problem because technically the routes don’t contain index.html files for them. If I navigate within my site, it works. If I go to, for example, <a href="https://atridad.dev/post/1" target="_blank" rel="noopener noreferrer nofollow ugc">https://atridad.dev/post/1</a>, it doesn’t work at all. Is this something we can have added or is there something I’m missing in config?</p>
<p dir="auto"><a class="plugin-mentions-group plugin-mentions-a" href="/groups/staff" aria-label="Profile: staff">@<bdi>staff</bdi></a></p>
]]></description><link>https://forum.cloudron.io/topic/5984/request-support-for-html5-history</link><generator>RSS for Node</generator><lastBuildDate>Sun, 14 Jun 2026 10:53:10 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/5984.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 11 Nov 2021 06:21:56 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Request: Support for HTML5 History on Fri, 18 Mar 2022 20:18:46 GMT]]></title><description><![CDATA[<p dir="auto">I haven't actually chimed in on this since posted I guess. Whoops...</p>
<p dir="auto">Yeah my ask would maybe be the ability to add redirects based on status codes. As was mentioned, for example, any 404 could route to index.html (or any file one wants to specify). Just gives more options. Like this in cloud front, for instance:<br />
<img src="/assets/uploads/files/1647634717369-screen-shot-2022-03-18-at-2.18.11-pm-resized.png" alt="Screen Shot 2022-03-18 at 2.18.11 PM.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.cloudron.io/post/44931</link><guid isPermaLink="true">https://forum.cloudron.io/post/44931</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Fri, 18 Mar 2022 20:18:46 GMT</pubDate></item><item><title><![CDATA[Reply to Request: Support for HTML5 History on Thu, 11 Nov 2021 16:31:34 GMT]]></title><description><![CDATA[<p dir="auto">I guess we need a "default handler" which is functionally same as 404 page.</p>
]]></description><link>https://forum.cloudron.io/post/39129</link><guid isPermaLink="true">https://forum.cloudron.io/post/39129</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 11 Nov 2021 16:31:34 GMT</pubDate></item><item><title><![CDATA[Reply to Request: Support for HTML5 History on Thu, 11 Nov 2021 14:47:52 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nebulon" aria-label="Profile: nebulon">@<bdi>nebulon</bdi></a> said in <a href="/post/39112">Request: Support for HTML5 History</a>:</p>
<blockquote>
<p dir="auto">I guess somehow this can already made to work if you rename your index.html to 404.html</p>
</blockquote>
<p dir="auto">That could actually work.</p>
<p dir="auto">The challenge with single page apps is that you need rewrite rules to make requests to <code>/somepath/page</code> actually be handled by your <code>index.html</code>.</p>
]]></description><link>https://forum.cloudron.io/post/39118</link><guid isPermaLink="true">https://forum.cloudron.io/post/39118</guid><dc:creator><![CDATA[fbartels]]></dc:creator><pubDate>Thu, 11 Nov 2021 14:47:52 GMT</pubDate></item><item><title><![CDATA[Reply to Request: Support for HTML5 History on Thu, 11 Nov 2021 12:50:53 GMT]]></title><description><![CDATA[<p dir="auto">I am not sure I understand what the issue and the expected behavior is.</p>
<p dir="auto">So my guess is, you have a client side app which is at the root, some index.html there will be served up. Now further you navigate and your (in this case vue) app doesn't use a hash style navigation, but overloads the browser location with paths, which are just known to the app?</p>
<p dir="auto">If this is the case, then the only thing I can think of is to somehow add a config option to surfer, which essentially means it will always server up a specified file, regardless of the path, if we hit otherwise a 404? I guess somehow this can already made to work if you rename your index.html to 404.html (quite the strange workaround if that works and is what you expected of course <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f604.png?v=13d69e59554" class="not-responsive emoji emoji-android emoji--smile" style="height:23px;width:auto;vertical-align:middle" title=":D" alt="😄" /> )</p>
]]></description><link>https://forum.cloudron.io/post/39112</link><guid isPermaLink="true">https://forum.cloudron.io/post/39112</guid><dc:creator><![CDATA[nebulon]]></dc:creator><pubDate>Thu, 11 Nov 2021 12:50:53 GMT</pubDate></item></channel></rss>