Open suttin opened 7 months ago
I've opened up an issue with amplipi as well, I'm unsure of what the intended behavior is supposed to be from the api webserver. https://github.com/micro-nova/AmpliPi/issues/538
This PR should be closed. The API path change was a minor bug in 0.3.0 and has been fixed in all subsequent versions.
It appears that the path has been updated in 0.3.0 to no longer accept the trailing / on the api path. When going to amplipi:80/api/ you get a json body that says not found.
I've reverted my instance to 0.2.1 and can confirm that amplipi:80/api works without the last forward slash
Or to put it another way:
v0.2.1 amplipi.local/api and amplipi.local/api/ both work. v0.3.0 amplip.local/api works and amplipi.local/api/ does not work.