Author: Carl Helmertz <[email protected]> Date: Fri Oct 18 11:08:36 2013 +0200 Committer: Lars Michelsen <[email protected]> Commit-Date: Wed Nov 20 18:59:53 2013 +0100
ajax.js: Don't set content-length or connection headers for XHRs These headers are removed, and set by the browser for security reasons [1]. These lines showed up as errors in Chrome's error console. 1: http://www.w3.org/TR/XMLHttpRequest/#the-setrequestheader()-method Signed-off-by: Carl Helmertz <[email protected]> Signed-off-by: Lars Michelsen <[email protected]> --- share/frontend/nagvis-js/js/ajax.js | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/share/frontend/nagvis-js/js/ajax.js b/share/frontend/nagvis-js/js/ajax.js index 7b33a90..8d5531e 100644 --- a/share/frontend/nagvis-js/js/ajax.js +++ b/share/frontend/nagvis-js/js/ajax.js @@ -436,8 +436,6 @@ function postSyncRequest(sUrl, sParams) { // Set post specific options oRequest.setRequestHeader('Content-Type', 'application/x-www-form-urlencoded'); - oRequest.setRequestHeader("Content-length", sParams.length); - oRequest.setRequestHeader("Connection", "close"); try { oRequest.send(sParams); ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Nagvis-checkins mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagvis-checkins
