bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

With a NULL target argument, NPN_GetURLNotify does not cause NPP_Notify to be called if the URL cannot be retrieved




14 years ago
13 years ago


(Reporter: Carlo Bonamico, Assigned: Peter Lubczynski)



Firefox Tracking Flags

(Not tracked)




14 years ago
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113

NPP_URLNotify is never called if the URL requested with NPN_GetURLNotify() is 
not valid/available (e.g. missing file (error 404) or wrong server name/address)

Netscape 4.x shows the correct behavior 

It applies also to Netscape 6/6.1/7/7.1 and all Mozilla builds up to the 
current (1.6) included.

This bug makes impossible for a plugin to detect that a needed resource is 
missing, and then to provide the user with an explaination or an alternative.

Reproducible: Always
Steps to Reproduce:
1. write a plugin that calls NPN_GetURLNotify 
2. call the function NPN_GetURLNotify with a non-existent URL(missing 
file/wrong server name, etc.)

Actual Results:  
NPP_URLNotify is never called if the requested URL is not valid/available (e.g. 
missing file (error 404) or wrong server name/address)

Expected Results:  
call the plugin callback NPP_URLNotify 
pass parameter reason = NPRES_NETWORK_ERR | NPRES_USER_BREAK	

The bug was verified on Windows 98/2000, but is likely to apply to all 

Comment 1

14 years ago
It is probably related to bug 117766


14 years ago
Keywords: 4xp
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.