Forum Discussion
- bmcdougallCommunity Managermike082 is this something you could help with?
- mike082Novice IHi jophyjohn. To understand this, you are getting a sporadic 404 error just calling the API version endpoint that lists the API versions available on the array? Or is it a specific API version endpoint you are calling? Is the API call timing out?
- mboeckelmannNovice Ithe path is /api/api_version
- mboeckelmannNovice I```curl -k https://gse-array01/api/api_version {"version":["1.0","1.1","1.2","1.3","1.4","1.5","1.6","1.7","1.8","1.9","1.10","1.11","1.12","1.13","1.14","1.15","1.16","1.17","1.18","1.19","2.0","2.1","2.2","2.3","2.4","2.5","2.6","2.7","2.8","2.9","2.10","2.11","2.13","2.14","2.15","2.16","2.17","2.19","2.20","2.21","2.22","2.23","2.24","2.25","2.26","2.27","2.28","2.29","2.30","2.31","2.32","2.33","2.34","2.35","2.36"]}```
- jophyjohnNovice II could resolve the issue by myself. Even though the /api_version api doesn’t require credentials, if we pass basic auth credentials to the api call, it breaks. This is the new behavior that I have seen with this api.
- jophyjohnNovice IAll good now. Thanks for checking
- mboeckelmannNovice Ijophyjohn not sure what you mean? the api_version endpoint is a GET. anything auth related is a POST on FA. GET requests should not have auth.
- mboeckelmannNovice Ieven still, just tested api_version with auth(uname/pw) and it still comes back 200 OK.
- jophyjohnNovice IIt was the case earlier but recently (may be after recent upgrade) I saw a difference
- jophyjohnNovice IAnyway I could resolve it by removing the basic auth