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

Return HTTP response status codes from Cloud Code #9479

Open
BobyIlea opened this issue Dec 9, 2024 · 1 comment · May be fixed by #9500
Open

Return HTTP response status codes from Cloud Code #9479

BobyIlea opened this issue Dec 9, 2024 · 1 comment · May be fixed by #9500
Labels
bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature

Comments

@BobyIlea
Copy link

BobyIlea commented Dec 9, 2024

New Feature / Enhancement Checklist

Current Limitation

The HTTP status codes returned by cloud code in the response's header can not be determined in the cloud functions.

Feature / Enhancement Description

Ability to set the HTTP status code in the response header of a cloud function call.

Example Use Case

Set a 401 status code in the response header when an unauthenticated user tries to access unauthorised data.

Alternatives / Workarounds

Currently we can manually set any information in the response body and mimic the status code functionality by manually parsing and handling the data and logic.

3rd Party References

All backends should have this ability.

Copy link

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added type:feature New feature or improvement of existing feature bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) labels Dec 9, 2024
@dblythy dblythy linked a pull request Dec 23, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants