Server should warn clients when using unexpected fields in requests.

[grim-i-am]

What Git revision are you using?

v5.3.0 binary

What operating system are you using, and which version?

• Linux / Ubuntu
• Linux / Other
• OSX
• Windows

Describe what the problem is?

When calling "Query/FindIntersect/RequestNext" methods with a reflection parameter, the reflection object is not sent to onMessage handler.

What should be the expected behavior?

Reflection parameter should always be reflected.

[KtorZ]

I have never observed such behavior 🤔 , are you setting the right parameter? In requests, the reflection parameter is called mirror. Settings reflection as a parameter on requests will have no effect.

[grim-i-am]

Sorry, my mistake

[KtorZ]

I think it's still worth adding some little code in the query parser to reject requests which would contain additional parameters, and in particular, a reflection parameter.

Mind if I rename the ticket to reflect this?

[grim-i-am]

Mind if I rename the ticket to reflect this?

not at all, be my guest!