You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Documentation on protocol page pointing to endpoint that does not respond #14
For example, the protocol lists an example such as:
Request: curl https://bridge.simplefin.org/simplefin/info
Response:
{
"versions": ["1.0-draft"],
}
However, doing that doesn't return anything. But this works: curl https://beta-bridge.simplefin.org/simplefin/info
Which returns:
{"versions":["1.0-draft"]}
Also the QuickStart mentions the sample token of aHR0cHM6Ly9icmlkZ2Uuc2ltcGxlZmluLm9yZy9zaW1wbGVmaW4vY2xhaW0vZGVtbw== which decodes to https://bridge.simplefin.org/simplefin/claim/demo (and in theory should return https://user123:pass456@bridge.simplefin.org/simplefin via curl), but it doesn't behave like so. Instead, calling curl returns a redirect to beta-bridge.simplefin.org.
Likewise, calling curl "https://user123:pass456@bridge.simplefin.org/simplefin/accounts" also returns no data due to this redirect.
On the other hand, if I decode aHR0cHM6Ly9iZXRhLWJyaWRnZS5zaW1wbGVmaW4ub3JnL3NpbXBsZWZpbi9jbGFpbS9ERU1P into https://beta-bridge.simplefin.org/simplefin/claim/DEMO, provided by the Developer's Guide, and then curl -X POST "https://beta-bridge.simplefin.org/simplefin/claim/DEMO", I successfully retrieve https://demo:demo@beta-bridge.simplefin.org/simplefin and then I'm able to follow the quick start with ACCESS_URL="https://demo:demo@beta-bridge.simplefin.org/simplefin"
I guess the question is, is it intentional to no longer hold the simplefin bridge server at bridge.simplefin.org? If so, should documentation be updated to point to beta-bridge.simplefin.org?
If you add the -L flag to your curl commands, does everything work? The intent is to keep things at bridge. but while in beta to have that redirect to beta-bridge. transparently.
Hey, sorry for the late reply. This is what I get on both Linux and MacOS when I execute the command curl -L https://bridge.simplefin.org/simplefin/info or curl -L "https://user123:pass456@bridge.simplefin.org/simplefin/accounts":
Activity
iffy commentedon Jun 12, 2023
If you add the
-Lflag to yourcurlcommands, does everything work? The intent is to keep things atbridge.but while in beta to have that redirect tobeta-bridge.transparently.AJ-Ianozi commentedon Jun 17, 2023
Hey, sorry for the late reply. This is what I get on both Linux and MacOS when I execute the command
curl -L https://bridge.simplefin.org/simplefin/infoorcurl -L "https://user123:pass456@bridge.simplefin.org/simplefin/accounts":