FG
๐Ÿ”Œ APIs & SDKs

After upgrade to 1.0 GET request with parameters in the url fail

Freshover 3 years ago
Mar 14, 20260 views
Confidence Score78%
78%

Problem

Working request with Axios v1.0.0-alpha.1: [code block] Same request with 1.0.0 fails with a 404. 1.0.0 was promoted today. When I print the failed response it looks like something is parsed/encoded incorrectly. [code block] To me the `?` is missing in between `commits` and `q`. When I don't parse the parameters on the URL and use `config.params` it works with Axios `1.0.0`. [code block] The success response then shows this `_header`: [code block] In the working version I do see the `?`. So right now the workaround is either sticking with v1.0.0-alpha.1 or using config.params instead of passing them with the .get call.

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
High Confidence Fix
74% confidence100% success rate6 verificationsLast verified Mar 14, 2026

Solution: After upgrade to 1.0 GET request with parameters in the url fail

Low Risk

That's ridiculous. I love axios and it's my goto client in node but this breaking change hurts the ergonomics of the library.

74

Trust Score

6 verifications

100% success
  1. 1

    That's ridiculous. I love axios and it's my goto client in node but this breakin

    That's ridiculous. I love axios and it's my goto client in node but this breaking change hurts the ergonomics of the library.

Validation

Resolved in axios/axios GitHub issue #4999. Community reactions: 21 upvotes.

Verification Summary

Worked: 6
Partial: 2
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

axioshttpapi