Skip to content

Add missing Content-Type headers in public api #372

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.

Sign up for GitHub

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

Jump to bottom
Open
skipi opened this issue Jun 9, 2025 · 0 comments
Open

Add missing Content-Type headers in public api #372

skipi opened this issue Jun 9, 2025 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@skipi
Copy link
Contributor

skipi commented Jun 9, 2025 •
edited
Loading

Is your improvement proposal related to a problem? Please describe.

Currently, only some responses from the public API have a Content-Type header set. This can lead to issues when the requester expects a specific content type and it is not provided.

Describe the solution you'd like

Add Content-Type headers to all responses from the public API, ensuring that they are set to the appropriate type based on the content being returned (e.g., application/json for JSON responses).

Describe alternatives you've considered

No response

Additional context
@skipi skipi added enhancement New feature or request good first issue Good for newcomers labels Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@skipi