[GH-ISSUE #3361] PWA not retrieving status-400 codes #1122

New issue

Closed

opened 2026-03-16 18:43:53 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 18:43:53 +03:00

Owner

Originally created by @Batimius on GitHub (Sep 15, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3361

Discussed in https://github.com/hoppscotch/hoppscotch/discussions/3309

^{Originally posted by Batimius September 1, 2023}
Hello there. So, I was testing a local application (an app running on http://localhost:3000), and in my application, I return a status-400 response when the user does not provide the appropriate data to the API endpoint. When running the requests through Hoppscotch, any request that would end up in a status-400 response would give me a "Could not send request" screen. It wouldn't give me the response itself, but it would rather just display that it could not send the request.

I am unsure whether this is an intended behavior or not. I am using the extension and I have whitelisted http://localhost:3000, so I am unsure why this is an issue. If there is a way for me to fix this, please let me know. I am running Hoppscotch as a PWA from hoppscotch.io. That is all. Thank you for your time and help, they are truly appreciated.

Just like mentioned in the discussion above, status-400 codes are never processed by the Hoppscotch application (PWA). Any status-400 request ends up in a "could not send request" screen. Since this seems to be unintentional, I decided to open an issue thread. Please let me know if this is a known issue or not. Thank you for the time and support.

Originally created by @Batimius on GitHub (Sep 15, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3361 ### Discussed in https://github.com/hoppscotch/hoppscotch/discussions/3309 <div type='discussions-op-text'> <sup>Originally posted by **Batimius** September 1, 2023</sup> Hello there. So, I was testing a local application (an app running on `http://localhost:3000`), and in my application, I return a status-400 response when the user does not provide the appropriate data to the API endpoint. When running the requests through Hoppscotch, any request that would end up in a status-400 response would give me a "Could not send request" screen. It wouldn't give me the response itself, but it would rather just display that it could not send the request. I am unsure whether this is an intended behavior or not. I am using the extension and I have whitelisted `http://localhost:3000`, so I am unsure why this is an issue. If there is a way for me to fix this, please let me know. I am running Hoppscotch as a PWA from hoppscotch.io. That is all. Thank you for your time and help, they are truly appreciated.</div> Just like mentioned in the discussion above, status-400 codes are never processed by the Hoppscotch application (PWA). Any status-400 request ends up in a "could not send request" screen. Since this seems to be unintentional, I decided to open an issue thread. Please let me know if this is a known issue or not. Thank you for the time and support.

kerem closed this issue

2026-03-16 18:43:58 +03:00

kerem commented

2026-03-16 18:44:04 +03:00

Author

Owner

@liyasthomas commented on GitHub (Sep 15, 2023):

Thanks for submitting the issue. We have an open PR to fix this issue on our Browser Extension repository: https://github.com/hoppscotch/hoppscotch-extension/pull/227.

Expect a hotfix as early as next week. Thanks for being patient.

@liyasthomas commented on GitHub (Sep 15, 2023): Thanks for submitting the issue. We have an open PR to fix this issue on our Browser Extension repository: https://github.com/hoppscotch/hoppscotch-extension/pull/227. Expect a hotfix as early as next week. Thanks for being patient.

kerem commented

2026-03-16 18:44:09 +03:00

Author

Owner

@Batimius commented on GitHub (Sep 15, 2023):

Thanks for submitting the issue. We have an open PR to fix this issue on our Browser Extension repository: hoppscotch/hoppscotch-extension#227.

Expect a hotfix as early as next week. Thanks for being patient.

Thank you for the fast reply. Please @ me (or reply / close this issue) when this is fixed so I know when I can start using Hoppscotch again. Cheers!

@Batimius commented on GitHub (Sep 15, 2023): > Thanks for submitting the issue. We have an open PR to fix this issue on our Browser Extension repository: [hoppscotch/hoppscotch-extension#227](https://github.com/hoppscotch/hoppscotch-extension/pull/227). > > Expect a hotfix as early as next week. Thanks for being patient. Thank you for the fast reply. Please @ me (or reply / close this issue) when this is fixed so I know when I can start using Hoppscotch again. Cheers!

kerem commented

2026-03-16 18:44:14 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 15, 2023):

We've recently patched this issue, hence closing the ticket. Updated the browser extension to the latest version.

Feel free to re-open if the issue persists. cc: @Batimius

@liyasthomas commented on GitHub (Oct 15, 2023): We've recently patched this issue, hence closing the ticket. Updated the browser extension to the latest version. Feel free to re-open if the issue persists. cc: @Batimius

kerem referenced this issue

2026-03-17 00:43:34 +03:00

[PR #1122] [CLOSED] [Snyk] Security upgrade firebase-admin from 8.6.0 to 9.0.0 #3079