You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This line alters keys that begin with a slash or contain more than one slash in a row.
E.g.1: A call to /service/yourservice/purge//keyStartingWithASlash
becomes /service/yourservice/purge/keyStartingWithASlash
E.g.2: A call to /service/yourservice/purge/keyWithDouble//Slash
becomes /service/yourservice/purge/keyWithDouble/Slash
It appears the intended behavior at this line is something more along the lines of "add or remove slashes as needed at the joined location when merging the host path with the api path" or in code: 57dedaf
Tangentially related:
Due to #14, it's worth noting that Fastly explicitly states that keys should not be URL encoded. If/when a fix for #14 does URL encode data parameters to the Fastly API, that fix must not URL encode cache keys.
The text was updated successfully, but these errors were encountered:
kf6nux
pushed a commit
to kf6nux/go-fastly
that referenced
this issue
Feb 8, 2017
This line alters keys that begin with a slash or contain more than one slash in a row.
E.g.1: A call to
/service/yourservice/purge//keyStartingWithASlash
becomes
/service/yourservice/purge/keyStartingWithASlash
E.g.2: A call to
/service/yourservice/purge/keyWithDouble//Slash
becomes
/service/yourservice/purge/keyWithDouble/Slash
It appears the intended behavior at this line is something more along the lines of "add or remove slashes as needed at the joined location when merging the host path with the api path" or in code: 57dedaf
Tangentially related:
Due to #14, it's worth noting that Fastly explicitly states that keys should not be URL encoded. If/when a fix for #14 does URL encode data parameters to the Fastly API, that fix must not URL encode cache keys.
The text was updated successfully, but these errors were encountered: