-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use Inspector on Basic Auth'd endpoints #445
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Stale undo. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Stale undo. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Stale nope, undo. |
RPC APIs prevalently require some kind of authentication, often HTTP Basic Auth.
It's currently not even possible to test RPCs and their OpenRPC descriptions:
Well, yes it is! What's the error?!?I do understand that it's
Window.fetch
acting up, and OpenRPC Playground merely provides context. This seems to be a relatively recent issue with browsers: https://medium.com/@lmakarov/say-goodbye-to-urls-with-embedded-credentials-b051f6c7b6a3Any workarounds? Did I miss the user/password fields in
Add transport
dialogs?Removing the
dummy-user:test-password@
from the URL just producesNetworkError when attempting to fetch resource.
— the RPC call I'm trying to make is never made (i.e. not even a 401 error).Repro steps
printf "dummy-user:$(openssl passwd -apr1 test-password)\n" > /tmp/test.htpasswd
list_pets
(doesn't matter) from the Inspector tohttp://localhost/rpc
Expected behavior
There is a way to test Basic Auth'd RPC endpoints.
Actual behavior
No working way exists.
Desktop
The text was updated successfully, but these errors were encountered: