Worklight:WL.Client.addGlobalHeader()无效

时间:2013-10-09 12:28:15

标签: http-headers ibm-mobilefirst http-caching

当我添加行

WL.Client.addGlobalHeader("MyCustomHeader","abcdefgh");

在我的主要js文件中,如此

function wlCommonInit(){

WL.Client.addGlobalHeader("MyCustomHeader","abcdefgh");
    (...)

就像它在文档中所描述的那样(http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m5/topic/com.ibm.worklight.help.doc/apiref/r_wl_client_addglobalheader.html),之后所有请求发送都没有任何影响:

GET /apps/services/preview/MobileOPMClient/common/0/default/images/icons/icon_settings.png             
HTTP/1.1
Host: localhost:8080
Connection: keep-alive
Accept: image/webp,*/*;q=0.8
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/30.0.1599.66 Safari/537.36
Referer: http://localhost:8080/apps/services/preview/MobileOPMClient/common/0/default/MobileOPMClient.html
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8,de;q=0.6
Cookie: JSESSIONID=1e1fig7holfdpeuc46w6jmrph; testcookie=oreo

为什么没有行

MyCustomHeader: abcdefgh

背景:我想允许本地缓存javascript文件以在chrome中调试它们。

SPYRO

1 个答案:

答案 0 :(得分:2)

为WL客户端API发出的请求添加了全局标头,例如WL.Client.connect(),WL.Client.invokeProcedure()等。