requestPasswordReset email link (“Verify Email” button) redirects to internal server error

[rjcodedev]

New Issue Checklist

• Report security issues confidentially.
• Any contribution is under this license.
• Before posting search existing issues.

Issue Description

When configuring Parse Server 9.3.0-alpha.3 with appId = product and appName = Product™, I encounter an internal server error on the “Request Password Reset” page.

but with same config it's work perfectly fine with version 8.6.2

Steps to reproduce

1. provide appId: product, appName: Product™ in config
2. Parse.User.requestPasswordReset(username) call this method for forgot password.
3. Then click on verify email button from forgot password email

Actual Outcome

got error {"code": 1, "message": "internal server error."} on request password reset

Expected Outcome

It should provide password change screen

Server

• Parse Server version: 9.2.0
• Operating system: windows
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): JavaScript
• SDK version: 8.1.0

Logs

TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["x-parse-page-param-appname"]
    at ServerResponse.setHeader (node:_http_outgoing:703:3)
    at ServerResponse.header (C:\new\apps\product\node_modules\express\lib\response.js:686:10)
    at C:\new\apps\product\node_modules\parse-server\lib\PromiseRouter.js:167:17
    at Array.forEach (<anonymous>)
    at C:\new\apps\product\node_modules\parse-server\lib\PromiseRouter.js:166:39

[parse-github-assistant]

🚀 Thanks for opening this issue!

ℹ️ You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

I guess it's because of the ™ symbol. Probably an encoding issue. If you remove the symbol, do you still get the error?

[rjcodedev]

Hey @mtrezza ,

It’s working without ™, but I’d like it to support it as well. Could you make the same changes as in 8.6.2 so it works with it?

[rjcodedev]

Hey @mtrezza ,

Is there any update on this ?

[mtrezza]

Nope, requires investigation

[rjcodedev]

hey @mtrezza ,

I would greatly appreciate it if you could please prioritize and fix this issue at the earliest.

[mtrezza]

What's the last Parse Server version in which this issue does not occur, and the first version in which the issue occurs for you? Also test alpha versions.