Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] /status.html endpoint fails when statusFilePath is not set #23809

Open
2 of 3 tasks
lhotari opened this issue Jan 3, 2025 · 1 comment
Open
2 of 3 tasks

[Bug] /status.html endpoint fails when statusFilePath is not set #23809

lhotari opened this issue Jan 3, 2025 · 1 comment
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@lhotari
Copy link
Member

lhotari commented Jan 3, 2025

Search before asking

  • I searched in the issues and found nothing similar.

Read release policy

  • I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

any released version

Minimal reproduce step

  1. set statusFilePath to empty in standalone.conf
  2. start pulsar standalone with bin/pulsar standalone
  3. go to http://localhost:8080/status.html (or use curl http://localhost:8080/status.html)

What did you expect to see?

that /status.html endpoint returns "OK" when statusFilePath is not set and the broker is ready.

What did you see instead?

The /status.html will always return 404 failure

Anything else?

There's also invalid default configuration in standalone.conf:

statusFilePath=/usr/local/apache/htdocs

This value doesn't make any sense. The default value should be empty (which results in null).

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@lhotari lhotari added the type/bug The PR fixed a bug or issue reported a bug label Jan 3, 2025
@lhotari
Copy link
Member Author

lhotari commented Jan 3, 2025

@yyj8 Would you be interested in addressing this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant