<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Possibility to reserve an url following a regex</title>
  <link rel="self" href="https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=121855806" />
  <subtitle>Possibility to reserve an url following a regex</subtitle>
  <id>https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=121855806</id>
  <updated>2026-04-17T14:54:18Z</updated>
  <dc:date>2026-04-17T14:54:18Z</dc:date>
  <entry>
    <title>RE: RE: Possibility to reserve an url following a regex</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121858216" />
    <author>
      <name>Eric DARIEL</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121858216</id>
    <updated>2025-10-21T05:12:37Z</updated>
    <published>2023-06-12T12:55:12Z</published>
    <summary type="html">&lt;p&gt;Yes, it is exactly what we want.&lt;/p&gt;
&lt;p&gt;It now works for us.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;Thanks Fabian.&lt;/p&gt;</summary>
    <dc:creator>Eric DARIEL</dc:creator>
    <dc:date>2023-06-12T12:55:12Z</dc:date>
  </entry>
  <entry>
    <title>RE: Possibility to reserve an url following a regex</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121857803" />
    <author>
      <name>Fabian Bouché</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121857803</id>
    <updated>2023-06-12T12:52:54Z</updated>
    <published>2023-06-12T11:14:08Z</published>
    <summary type="html">&lt;p&gt;Hello Eric,&lt;/p&gt;
&lt;p&gt;When you register a custom element, you can set a friendly URL mapping.&lt;/p&gt;
&lt;p&gt;Suppose you pur &amp;quot;foo&amp;quot; in that field, then you will be
  allowed to implement a router supporting this kind of URLs:&lt;/p&gt;
&lt;p&gt;http://localhost:8080/web/guest/home/-/foo/contracts/12&lt;/p&gt;
&lt;p&gt;/-/ is the friendly URL separator which makes it possible for Liferay
  to identify where the layout part of the URL ends.&lt;/p&gt;
&lt;p&gt;When you register such friendly URL mapping for custom elements, the
  page will not reload when you follow links with that pattern.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Fabian&lt;/p&gt;</summary>
    <dc:creator>Fabian Bouché</dc:creator>
    <dc:date>2023-06-12T11:14:08Z</dc:date>
  </entry>
  <entry>
    <title>Possibility to reserve an url following a regex</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121855805" />
    <author>
      <name>Eric DARIEL</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121855805</id>
    <updated>2025-10-21T05:12:37Z</updated>
    <published>2023-06-11T15:37:27Z</published>
    <summary type="html">&lt;p&gt;Hello,&lt;br&gt; I am trying to configure a route in my angular
  customElement, but if I change the url, Liferay think I am in an other
  page.&lt;br&gt; Example, we have a page /contracts where we can see a list
  of all the contracts and we want to see the detail of a contract 12 in
  the page /contracts/12, Liferay try to find this page but we want to
  stay on the page /contracts with the url /contracts/12 and our angular
  app will show the detail of the contract 12.&lt;br&gt; Is it possible to
  ignore the end of an url ?&lt;br&gt; For a site we can redirect or create
  alias but we want to do this for all our sites (we have a site
  template)&lt;br&gt; It would be great if a customElement can
  &amp;quot;reserve&amp;quot; an url matching a regex like we can do with a
  standard portlet (friendlyurl route)&lt;/p&gt;
&lt;p&gt;Eric.&lt;/p&gt;</summary>
    <dc:creator>Eric DARIEL</dc:creator>
    <dc:date>2023-06-11T15:37:27Z</dc:date>
  </entry>
</feed>
