Skip to content

file/content api returns 401 on internal podman network but works from external #4827

@jcaplan

Description

@jcaplan

I have opengrok container with port 8080 exposed on the podman network and mapped to 9000 on host network.

If I do this externally it works: curl http://hostname.domain:9000/api/v1/file/content?path=/path/to/file
But from another container using the internal port and hostname: curl http://opengrok:8080/api/v1/file/content?path=/path/to/file then I get:

<!doctype html><html lang="en"><head><title>HTTP Status 401 – Unauthorized</title>
<style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style>
</head><body><h1>HTTP Status 401 – Unauthorized</h1><hr class="line" /><p>
<b>Type</b> Status Report</p>
<p><b>Message</b> Unauthorized</p><p><b>Description</b>
 The request has not been applied to the target resource because it lacks valid authentication credentials for that resource.</p>
<hr class="line" /><h3>Apache Tomcat/10.1.43</h3></body></html>

I'm pretty stumped what could be the difference

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions