Not able to introduce new spa excluded paths if necessary

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.1.X, 7.2.X, 7.3.X, Master
• Fix Version/s: 7.1.10 DXP FP26, 7.1.10.7 SP7, 7.1.X, 7.2.10 DXP FP14, 7.2.10.5 DXP SP5, 7.2.X, 7.3.7 CE GA8, 7.3.10 DXP FP2, 7.3.X, 7.4.0 CE GA1, 7.4.13 DXP GA1, Master
• Component/s: SPA Engine (Senna)
• Labels:
  • ee-ts
  • liferay-dxp-71-sp7
  • liferay-dxp-72-sp5
  • liferay-fixpack-dxp-14-7210
  • liferay-fixpack-dxp-2-7310
  • liferay-fixpack-dxp-26-7110
• Branch Version/s:
  7.3.x, 7.2.x, 7.1.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/99068

Currenty the spa.excluded.path property from modules/apps/frontend-js/frontend-js-spa-web/src/main/resources/spa.properties contains the paths that spa does not handle.

All of them are related with documents.

Anyway, in a regular system it is not weird to serve documents direnctly using the web server.

In this case spa handles this links as regular internal links and breaks, for example, the pdf visualization.

To fix this we could include a new system configuration to allow users add more paths if needed.