This post is at: ForumGeneral Questions
2 posts / 0 new
Last post
lemcoe9
lemcoe9's picture
Joined: 2018/05/04
Points: 0

When using the `/apitest/` web-based API tool, I am able to get valid REST API responses from Thirdlane Multi-Tenant. However, when making these requests from anywhere else (including authenticated requests from Postman and from a PHP curl script on the server itself, I get a 502 Bad Gateway error. Please find attached the Dev Tools headers from the successful web-based request, and also attached the 502 Bad Gateway response that appears in Postman when I attempt to pass Basic authentication.

Looking at the successful responses in the browser, I cannot see any differences between how those are being executed versus how my PHP script passes the base64-encoded Basic authentication.

What is the trick to getting passed the 502 Bad Gateway error when hitting /api/ endpoints on Thirdlane MT?

Thank you!

AttachmentSize
Image icon screenshot2.png242.79 KB
Image icon screenshot1.png418.54 KB
lemcoe9
lemcoe9's picture
Joined: 2018/05/04
Points: 0

I figured it out. You need trailing slashes on the API URIs.

What a world.