New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and the Parse JS SDK.

Issue Description

If any of the Parse.find queries are executed, an Uncaught (in promise) Error: Failed to execute 'has' on 'Headers': Invalid name exception is raised when the request is received.

Steps to reproduce

1. Fetch a parse.min.js

 <script type="text/javascript" src="https://unpkg.com/parse/dist/parse.min.js"></script>

2. Initialization

 Parse.initialize(id, token);
 Parse.serverURL = 'https://parseapi.back4app.com/';

3. Run a query

 const refQuery = new Parse.Query(SomeSchemaName);
 refQuery
 .equalTo('someParam', someParamValue).limit(1000);
 .find() // without `find()` or any filter, the error be raised too
 .then((results) => {
 // ...
 })
 .catch((error) => {
 // The error will be raised
 });

Actual Outcome

Uncaught (in promise) Error: Failed to execute 'has' on 'Headers': Invalid name thrown at the below header check.

Expected Outcome

Query result will be retrieved.

Environment

Server

• Parse Server version: 6.2.0
• Operating system: not disclosed
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Back4App

Database

• System (MongoDB or Postgres): MongoDB
• Database version: 3.6.0
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Back4App

Client

• Parse JS SDK version: 7.0.0
• Chrome Version 141.0.7390.108 (Official Build) (arm64)
• MacOS 26.0.1

Logs

Parse server response

Image

Client debug log