내 커뮤니티 업적 표시줄을 확대합니다.

Submissions are now open for the 2026 Adobe Experience Maker Awards

Mark Solution

활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.

해결됨

NS_BINDING_ABORTED error in HTTFOX

Avatar

Level 2

Hi,

I hope somebody can help me here. We have been experiencing issues with when testing customlinks with Firefox with the httpfox plugin. When we click on the link with is tagged with an onclick we are seeing the image request in httpfox but is given a 403 NS_BINDING_ABORTED error.  The clicks seem to still show up in the reports but we would like to stop this error from appearing.

Thanks in advance

Brian

1 채택된 해결책 개

Avatar

정확한 답변 작성자:
Level 4

NS_BINDING_ABORTED error happens because the browser is navigated away from the page before it receives a response from adobe server. You can use a HTTP proxy tool like Fiddler or Charles to see the correct response code

This Adobe article explains about this in detail: http://adobe.ly/1op9SQ5

원본 게시물의 솔루션 보기

2 답변 개

Avatar

Level 10

Hi Brian,

 

It is a common issue. As JiMa explained it is due to the fact that either the adobe image request did not have enough time to be sent before the next webpage is loaded or the image request is ent correctly but the response was not received because the next webpage was loaded to fast.

 

1. With H code H.25 and above has updated the code to wait 500 ms before moving to the next page : http://microsite.omniture.com/t2/help/en_US/sc/implement/index.html#Manual_Link_Tracking_Using_Custo...

 

2.Another way to do it is to set up a timer to wait 500 ms before moving to next page. So send image request to adobe start timer (500 ms (I usually use 700ms)) then move to next page. The idea is that you will have to prevent the default action of the link first. 

 

3.The third solution is to open the link in a new tab target="_blank"

 

Best regards.

 

Alexis Cazes

Avatar

정확한 답변 작성자:
Level 4

NS_BINDING_ABORTED error happens because the browser is navigated away from the page before it receives a response from adobe server. You can use a HTTP proxy tool like Fiddler or Charles to see the correct response code

This Adobe article explains about this in detail: http://adobe.ly/1op9SQ5