# HTTP 404 when passing long JWT in query string

**URL:** <https://community.auth0.com/t/http-404-when-passing-long-jwt-in-query-string/64126>\
**Category:** JWT.io\
**Tags:** url, jwt\
**Created:** [June 8, 2021, 7:19pm UTC](https://community.auth0.com/t/http-404-when-passing-long-jwt-in-query-string/64126 "2021-06-08T19:19:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![steve-king-ky](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/steve-king-ky/32/29882_2.png) [@steve-king-ky](https://community.auth0.com/u/steve-king-ky)\
**Post date:** [June 8, 2021, 7:19pm UTC](https://community.auth0.com/t/http-404-when-passing-long-jwt-in-query-string/64126/1 "2021-06-08T19:19:54Z")

</div>

Our web application has a JWT that we want to send to other applications (the application itself is a portal). Initially we wanted to send it using the Authentication header (Bearer) but there’s no way to do this via, say, **window.open()**. We then decided to go with a querystring parameter. However, although the string is long (the token itself is a little over 2.3K), from what we can tell it’s still well under the maximum length for a URL. Oddly, instead of getting a HTTP 414 as one would expect, we get a 404.

The URL that’s being linked is a SharePoint site in this case; could it be that SP/IIS has some configuration that’s overriding this default behavior?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [June 9, 2021, 5:36pm UTC](https://community.auth0.com/t/http-404-when-passing-long-jwt-in-query-string/64126/3 "2021-06-09T17:36:11Z")

</div>

Hi @steve-king-ky,

Welcome to the Community!

Just a warning: [sending tokens in the qs can be considered risky.](https://stackoverflow.com/questions/32722952/is-it-safe-to-put-a-jwt-into-the-url-as-a-query-parameter-of-a-get-request)

The 404 would suggest you are sending to a page that doesn’t exist. It’s hard to say without knowing a bit more about what is going on. If you want to capture a HAR of the error happening and DM it to me I would be happy to take a look.

> **[Generate and Analyze HAR Files](https://auth0.com/docs/troubleshoot/troubleshooting-tools/generate-and-analyze-har-files)**
>
> Learn how to troubleshoot with HAR files and steps to generate a HAR file.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [July 13, 2021, 4:32pm UTC](https://community.auth0.com/t/http-404-when-passing-long-jwt-in-query-string/64126/4 "2021-07-13T16:32:43Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
