{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 贼婆χ 的问题《Sending a request back to server in onbeforeunload》','https://www.manongdao.com/q-918165.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
When a user edits a record in my application I track that they have it 'locked' to prevent another user from editing it until the first user closed the window (or saves).
I'm trying to send the request back to the server to unlock the record but it's not working in Firefox. The onbeforeunload event is called in script but it's not sending back the request to the server. Any ideas?
<body>
<script>
window.onbeforeunload = function (e) {
doUnlock();
}
function doUnlock() {
if (navigator.appName == 'Microsoft Internet Explorer') {
// works in IE (with an IFRAME)
utilFrame.location.href = "/unlock.do?recordId=" + recordId;
} else if (navigator.appName == 'Netscape') {
// None of this works....
//window.location.href = "/unlock.do?recordId=" + recordId;
var req = newXMLHttpRequest();
req.open("GET", "/unlock.do?recordId=" + recordId, true);
req.send();
} else {
// Works for chrome
window.open("/unlock.do?recordId=" + recordId);
}
}
</script>
You should look into using a time based lock. When a user starts editing a record lock it with a timestamp. Every 30 seconds send a ping from the user that the record should still be locked. If there is no ping for 60 seconds unlock the record.
Add a space between
newandXMLHttpRequest.On page unload, any pending (AJAX) requests are *cancelled. If you have to send an AJAX request to the server on unload, use a synchronous request (not recommended!!!):
I do not recommend the synchronous request, because the user interface blocks until the request has finished. That's not very user-friendly.