Problem with svg file (xml) through krakend with Gorilla Mux router

[ghpgmer]

I have been using Krakend and it has been working great. I ran into this problem while serving svg file (xml). I use Gorilla Mux as my router. I cannot use "string" for output_encoding as browser does not render the file. I tried using "no-op", but browser complains of "XML parsing error: no root element found".

The URL endpoint as such is correct - I tried serving it without krakend and it works fine (no XML error on browser).

I tried firefox, chrome and safari - all of them have a problem when I go through krakend.

I read the krakend documentation, there is "negotiate" option for other routers but not Mux.

How do I resolve the issue ? please let me know.

Just to check, I tried with html - I see the same problem. I think the browser does not understand what content type is being sent.

My krakend.json looks like this

{
    "endpoint": "a/b",
    "output_encoding": "no-op",
    "headers_to_pass":["*"],
    "method": "GET",
    "backend" [
        {
            "encoding": "no-op",
            "host": ["http://mylocalurl"],
            "url_pattern": "a/b"
        }
    ]
}

[github-actions]

Hi, thanks for bringing this issue to our attention.

Unfortunately, this issue has been marked invalid and will be closed.
The most common reasons for marking an issue or pull request as invalid is because:

• It's vague or not clearly actionable
• It contains insufficient details to reproduce
• It's plugin review or custom code review
• It does not use the issue template
• It's unrelated to the project (e.g., related to one of its libraries)
• It does not follow the technical philosophy of the project
• Violates our Code of Conduct
• It's about KrakenD functionalities (which uses and mantain Lura, but is not part of the Linux Foundation)

You can still make an edit or leave additional comments that lead to reopening this issue.

---

This is an automated comment. Responding to the bot or mentioning it won't have any effect

[github-actions]

This issue was marked as resolved a long time ago and now has been automatically locked as there has not been any recent activity after it. You can still open a new issue and reference this link.