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

jcaplan · 2025-08-21T23:46:47Z

jcaplan
Aug 21, 2025

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

jcaplan · 2025-08-22T05:25:39Z

jcaplan
Aug 22, 2025
Author

to clarify this problem doesn't happen with search:

different container:

# curl http://opengrok:8080/api/v1/search?def=func
{"time":9,"resultCount":1,"startDocument":0,"endDocument":1,"results":{"/path/to/file.c":[{"line":"<b>func</b> (void)","lineNumber":"145","tag":"function"}],}}

# curl http://opengrok:8080/api/v1/file/content?path=/path/to/file.c
<!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>

0 replies

vladak · 2025-08-22T12:57:01Z

vladak
Aug 22, 2025
Maintainer

I think this happens because the request to the exposed port appears to come from localhost while the other request does not. The API docs say up front:

Besides /suggester, /search, /system/ping and /metrics endpoints, everything is accessible from localhost only unless authentication bearer tokens are configured in the web application and used via the 'Authorization' HTTP header (within HTTPS connection).

For the auth token configuration directives see https://github.com/oracle/opengrok/wiki/Webapp-configuration#configuration-tunables

0 replies

Navigation Menu

Uh oh!

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

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Uh oh!

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

Uh oh!

jcaplan Aug 21, 2025

Replies: 2 comments

Uh oh!

jcaplan Aug 22, 2025 Author

Uh oh!

Uh oh!

vladak Aug 22, 2025 Maintainer

jcaplan
Aug 21, 2025

jcaplan
Aug 22, 2025
Author

vladak
Aug 22, 2025
Maintainer