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 }}
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.
It would be nice to allow auth headers to be added to the network operations that the plugin initiates. This would allow protected uris to serve the chcp content.
To allow authentication headers to be added, we need to refactor downloading mechanics to use a single method of downloading files, which can be configured with credentials, thus allowing authentication. This issue is opened to track development of such a feature.
Having a way to customize all headers is an open question. But initially, to not put too much burden on the users side, we will concentrate on specifying credentials. Other custom headers could be added in the future.
Another issue will be opened to track and discuss the user facing (js) api.
The text was updated successfully, but these errors were encountered:
davidovich
changed the title
Refactor download mechanics to allow future auth headers to be added
ios: Refactor download mechanics to allow future auth headers to be added
Nov 9, 2015
davidovich
changed the title
ios: Refactor download mechanics to allow future auth headers to be added
iOS: Refactor download mechanics to allow future auth headers to be added
Nov 9, 2015
It would be nice to allow auth headers to be added to the network operations that the plugin initiates. This would allow protected uris to serve the chcp content.
To allow authentication headers to be added, we need to refactor downloading mechanics to use a single method of downloading files, which can be configured with credentials, thus allowing authentication. This issue is opened to track development of such a feature.
Having a way to customize all headers is an open question. But initially, to not put too much burden on the users side, we will concentrate on specifying credentials. Other custom headers could be added in the future.
Another issue will be opened to track and discuss the user facing (js) api.
The text was updated successfully, but these errors were encountered: