Skip to content

Misc. bug: since 235f6e1 llama-server's main.js overwrites Authorization header so Web UI fails behind authenticating reverse proxy #10854

Closed
@vesath

Description

@vesath

Name and Version

$ ./llama.cpp/build/bin/llama-cli --version
version: 4336 (08ea539)
built with cc (GCC) 14.2.1 20240910 for x86_64-pc-linux-gnu

Operating systems

Linux

Which llama.cpp modules do you know to be affected?

llama-server

Problem description & steps to reproduce

I am running llama-server behind Caddy as an authenticating reverse proxy. Once authenticated, all requests should keep sending the "Authorization: Basic TOKEN" header. This was the case before commit 235f6e1.

Since commit 235f6e1, that Authorization header is only sent for the initial connection to "/" and not for subsequent completion requests. Instead, it gets overwritten with "Authorization: undefined".

The symptom is that all completion requests fail. The never reach the server. See the screenshots below. The main difference is at the bottom right under "Request headers" (Authorization).

1a31d0d-good
235f6e1-bad
symptom

I understand that 235f6e1 uses a new kind of completion requests which I'm not too familiar with. Please let me know if there's any further information I can provide to help diagnose this issue.

Cheers.

First Bad Commit

235f6e1

Relevant log output

No response

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