Skip to content

ESI renderer assumes current application is the target of the include #39130

@Bilge

Description

@Bilge

Symfony version(s) affected: 5.1.8
Description
ESI rendering sounds great in theory: I can work without an edge cache in development because Symfony will resolve the include by itself. However, calling out to an external resource does not work.

How to reproduce
{{ render_esi('https://example.com/foo') }} will error with:

An exception has been thrown during the rendering of a template ("No route found for "GET /foo"").

Despite the fact that example.com has nothing to do with our application, it ignores the hostname and just assumes the path can be found within our application.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy