Re:Authentication and the Have I Been Pwned API
by mehrdadn on Friday July 19, 2019 @01:58PM
(#20480953)
Funny thing is here I am wondering why he didn't pass a query parameter instead of altering the path or adding a header to version the API... does anyone know? It has the advantage of being clickable while not implying the resource is different.
[ Parent
| on HN ]
Re:Authentication and the Have I Been Pwned API
by floatingatoll on Friday July 19, 2019 @02:11PM
(#20481075)
One reason could be constructed by example, as:
<Location /v3>
vs. <LocationMatch ?[.*&]v=3(&|$)>
Which is to say that, depending on the application's coincidental design and structural choices over time, managing versions at /v1 /v2 /v3 might well be vastly easier for the "shoestring budget" operator than at /?v=1 /?v=2 /?v=3.
Re:Authentication and the Have I Been Pwned API
by mehrdadn on Friday July 19, 2019 @03:03PM
(#20481541)
It seems unlikely considering the other 3 were more drastically different and yet seen as pretty equally easy.
Re:Authentication and the Have I Been Pwned API
by Ayesh on Friday July 19, 2019 @11:18PM
(#20483986)
API versioning with query parameters is often an implementer nightmare.
Re:Authentication and the Have I Been Pwned API
by mehrdadn on Friday July 19, 2019 @11:25PM
(#20484014)
Why..? Does it break through too many abstraction layers?
Re:Authentication and the Have I Been Pwned API
by novaleaf on Friday July 19, 2019 @06:42PM
(#20483052)
one benefit of putting version in the path is it makes it easier for loadbalancers to direct traffic. like v3 could be served from different servers than v2