from some troubleshooting in the singer slack: &gt...
# singer-tap-development
e
from some troubleshooting in the singer slack:
figured this out, I was hitting a web application and my base URL had a single slash on the end of the URL. In my stream, I also had a single slash before the path so there was a double slash in the URL. This web application did a redirect to a single slash but downgraded your request to HTTP. Python request’s library strips out the Authorization header automatically to prevent SSL stripping attacks -- this one was fun to figure out heh
https://singer-io.slack.com/archives/C01KL2M763U/p1659463460090489
two things the SDK could certainly handle better and either warn or fail: • base url with a trailing slash • redirects
l
Tap-gitlab hit a similar bug with trailing slashes in URLs. https://github.com/MeltanoLabs/tap-gitlab/commit/a426d4ff3d9798aacdc06d54470a0083e6acca40 it would indeed be nice if the SDK could help prevent that sort of stuff