Clients that use __typename in queries with introspection disabled results in 403

[sherzberg]

We are working toward migrating from the apollo rust router with hive extension to this hive router and are seeing a difference in handling of introspection. We have introspection disabled in both router configs, but the hive-router returns 403 errors with a message of Introspection queries are disabled when making any query that uses __typename. The apollo router does not behave this way.

The docs here say __typename is used by the apollo client (I realize that is apollo docs, but I assume quite a few people are using that client):
https://www.apollographql.com/docs/apollo-server/schema/schema#the-__typename-field

Is this a known difference in handling of this feature? I'm not a graphql expert so not sure what the direction of this should be, just looking for some guidance.

[dotansimha]

Hi @sherzberg ! Thanks for reporting this. You are right, __typename is a unique case when it comes to introspection, as it's usually handled in a different way and not considred as introspection.

I'm working on a fix and additional tests in #872 :)

[sherzberg]

Awesome. We also didn't notice any logs from the router saying queries were being rejected due to this. Are there logs for this or can that be added as well?