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
The WebAgent may either act directly on the remote resource or via a proxy. For authenticated interaction it may be easier if the user can interact with the remote resource directly.
It will be easier to start off allowing only edits to the server that published the JS, then to deal with remote resources. This issue is a generalisation to issue #7 "Web Agent should not use Proxy to origin server" in that this is asking for an API that would also allow non proxied access to all resources.
The WebAgent may either act directly on the remote resource or via a proxy. For authenticated interaction it may be easier if the user can interact with the remote resource directly.
Otherwise the proxy must be able to authenticate for the user and support all methods.
Direct interaction with the resource on the other hand requires that the remote server authorise access to particular CORS agents.
The text was updated successfully, but these errors were encountered: