Pesquisas recentes

Sem pesquisas recentes

Why is the query string from the Chat auth flow returned with a hash (#) instead of a question mark?

Respondido
image avatar

Nicholas Walsh

Publicado 20 de set. de 2022

Why is the query string from the Chat auth flow returned to my callback URL with a hash (#) instead of a question mark? As anyone who develops enterprise level software should know, everything after # in the URL will be ignored by the server, so redirecting to a backend script means the query string cannot be parsed. What were you guys thinking?

Look at the response sent to the redirect uri here: https://support.zendesk.com/hc/en-us/articles/4408828740762-Chat-API-tutorial-Generating-an-OAuth-token-integrated-Chat-accounts-

0

1

1 comentário

Data
    image avatar

    Ramin Shokrizadeh

    Zendesk Product Manager

     
    Thanks for sharing your feedback on this. The article you are referring to was written in context of a front-end/browser based solution (which can handle reading the response fine with #) and we have another recommended solution for integrations via backend projects. 
     
    We recommend that you use the longer token generation method we have in the developer docs and the recommended grant flow: https://developer.zendesk.com/documentation/live-chat/getting-started/auth/#authorization-code-grant-flow
     
    All those responses come behind a ? (as in the examples provided) and it should address your concerns. If you have already tried this and you are still not getting what you want, let us know what is missing and I will pass your feedback to the engineering team who owns this part of the product.
     
    Thanks,
    Ramin
     

    0

    Por favor, entrar para comentar.

    Não encontrou o que estava procurando?

    Nova publicação