HTTP Headers for HTTPConnector in Script Based Value Set Provider
Hi everyone,
I saw this very good blog entry about using script based value set providers for querying remote resources
in javascript using the HTTPConnector:
http://jorgediazblog.wordpress.com/2012/06/27/work-item-customization-httpconector-and-oauth-in-rtc-4-0-for-oslc/
So the essence of this connector lies in the following class which can be found in the RTC SDK:
Inside the following parameters are defined:
//url: null,
//xpath: null,
//columnXpaths: null,
//columnIds: null,
//formBasedAuthenticationLoginURL: null,
//formBasedAuthenticationUsernameInputName: null,
//formBasedAuthenticationPasswordInputName: null,
//credentialsId: null,
//useBasicAuthentication: null,
//useFormAuthentication: null,
//useOAuth: null,
//userName: null,
//password: null,
//ignoreInvalidCertificates: null,
//log: null
Question: Where can I set HTTP headers?
This would be a very powerful feature. One example would be setting a content-type of "application/rdf+xml" and then just using the full capabilities the OSLC
I saw this very good blog entry about using script based value set providers for querying remote resources
in javascript using the HTTPConnector:
http://jorgediazblog.wordpress.com/2012/06/27/work-item-customization-httpconector-and-oauth-in-rtc-4-0-for-oslc/
So the essence of this connector lies in the following class which can be found in the RTC SDK:
com.ibm.team.workitem.api.common.connectors.HttpConnectorParameters();
Inside the following parameters are defined:
//url: null,
//xpath: null,
//columnXpaths: null,
//columnIds: null,
//formBasedAuthenticationLoginURL: null,
//formBasedAuthenticationUsernameInputName: null,
//formBasedAuthenticationPasswordInputName: null,
//credentialsId: null,
//useBasicAuthentication: null,
//useFormAuthentication: null,
//useOAuth: null,
//userName: null,
//password: null,
//ignoreInvalidCertificates: null,
//log: null
Question: Where can I set HTTP headers?
This would be a very powerful feature. One example would be setting a content-type of "application/rdf+xml" and then just using the full capabilities the OSLC
REST API gives you in terms of querying and selecting resources.