Added support for another proxy URL template where the proxy servers doesn't work with URL parameters. This is the case where the proxy server only works with the following template : http://proxy.com/{uri}. For example, https://proxy.linkeddatafragments.org/ does this.
We also added support for sending proxy request from http instead of requiring https. Maybe this might not be necessary, but it was needed in our use case. It would be nice if we could add an option to use http instead.
Accept headers weren't being sent correctly with the HTTP requests. Apparently, the problem lies in the Header interface from typescript where the specified accept types doesn't get parsed correctly. We fixed it by making use of native javascript Object.assign({}, header}. Hopefully it won't cause a security concern with the fix.
There are 3 fixes contained inside this PR.
Added support for another proxy URL template where the proxy servers doesn't work with URL parameters. This is the case where the proxy server only works with the following template :
http://proxy.com/{uri}. For example, https://proxy.linkeddatafragments.org/ does this.We also added support for sending proxy request from
httpinstead of requiringhttps. Maybe this might not be necessary, but it was needed in our use case. It would be nice if we could add an option to usehttpinstead.Accept headers weren't being sent correctly with the HTTP requests. Apparently, the problem lies in the
Headerinterface from typescript where the specified accept types doesn't get parsed correctly. We fixed it by making use of native javascriptObject.assign({}, header}. Hopefully it won't cause a security concern with the fix.