Periods in query strings seem to throw routing off

[atrauzzi]

http://localhost:8000/?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE1MDEzMDkyOTksInN1YiI6IjU5N2MxODliMzhmZTE5OTlhOTEzMjRiZCJ9.-YmntW5pTTmyke555OsOLJgeaPRHFIWrsjObsmZzfwQ

If I even just strip out the value from token and put any other value in, it's fine. As soon as I put a period . in there, it 404s. Something about having periods in query string variables seems to be messing things up.

[alampros]

It looks like this happens only in development mode, and is not limited to the query parameters - it affects the last path component as well:

http://localhost:8000/12.0/100/40.0
                        ^        ^
                      Fine     Breaks

[moisesv]

I keep getting the same error with the periods. I have tracked the problem down to:

/gatsby/src/commands/develop.js
line 120 in gatsby/commonad/develop.js

if (parsedPath.extname === `` || parsedPath.extname.startsWith(.html)) {

so using the example from above:
http://localhost:8000/?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE1MDEzMDkyOTksInN1YiI6IjU5N2MxODliMzhmZTE5OTlhOTEzMjRiZCJ9.-YmntW5pTTmyke555OsOLJgeaPRHFIWrsjObsmZzfwQ

which makes:
parsedPath.extname = '.-YmntW5pTTmyke555OsOLJgeaPRHFIWrsjObsmZzfwQ',

suggestions?

[KyleAMathews]

@moisesv would love a PR fixing this!

[alampros]

Did #2876 not fix this? Did you try it with gatsby@>1.9.108?

[moisesv]

Hi @alampros. I tried, did not fix it for me.

[alampros]

@moisesv - Does this still happen with [email protected]?

[KyleAMathews]

This seems fixed. Open a new issue if that's not the case!