You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
HttpExceptionFilter hides legitimate 4xx messages in production because its sensitive-word patterns are too broad #1488
In production sanitizeMessage replaces any message matching /token/i, /hash/i, /password/i, /duplicate/i, /database/i or /e\.?r\.?r\.?o\.?r\.?/i (which matches the plain word 'error') with a generic 'An unexpected error occurred', and it applies to client errors as well as 5xx. Messages such as 'Invalid hash format. Expected 64-character ...', 'Invalid refresh token' and validation errors that mention a password rule are replaced while keeping their 4xx status, so users and the frontend get no usable explanation.
Suggested fix
Sanitise only non-HttpException errors (and 5xx), return stable errorCodes for expected failures, and test the filter with real exception types.
Acceptance criteria
Client-facing 4xx messages are preserved in production
@demilade18-git has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Hi, I'd like to work on this issue.
I'm a software engineer with strong experience in JavaScript and building scalable web applications. I'm comfortable working across the stack, writing clean, maintainable code, and collaborating in open source environments.
I've reviewed the issue and I'm confident I can implement a solid solution while following the project's conventions.
Please assign this issue to me, I'd be happy to contribute.
@OffixialSydney has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Hello Maintainer, I’ve gone through the issue and its acceptance criteria carefully. I understand what needs to be implemented and am confident I can deliver a solution that aligns with the expected design.
Congratulations, @demilade18-git! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @demilade18-git: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🏆 @demilade18-git: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,228 total points). Track your full progress on GrantFox.
👏 Great work, @demilade18-git! Keep contributing to CodeGirlsInc.
😎 @demilade18-git: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Activity
demilade18-git commentedon Oct 17, 2026
@demilade18-git has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @demilade18-git to this issue.
OffixialSydney commentedon Oct 17, 2026
@OffixialSydney has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @OffixialSydney to this issue.
drips-wave commentedon Oct 17, 2026
Congratulations, @demilade18-git! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @demilade18-git: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
demilade18-git: bounded pagination + trusted client IP (#1488-#1491)
Merge pull request #1549 from demilade18-git/demilade-issues-1488-1491
grantfox-oss commentedon Oct 17, 2026
🎉 This issue has been marked as completed on GrantFox!
@demilade18-git's PR #1549 was approved and merged by @mftee.
🏆 @demilade18-git: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,228 total points). Track your full progress on GrantFox.
👏 Great work, @demilade18-git! Keep contributing to CodeGirlsInc.
drips-wave commentedon Oct 17, 2026
This issue has been completed by @demilade18-git as part of the Stellar Wave Program's 10th Wave 🥳
😎 @demilade18-git: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.