Confirmed users, Bureaucrats and Sysops emeriti
1,680
edits
NPAPI:HTTPRedirectHandling: Difference between revisions
→Specification
| Line 27: | Line 27: | ||
* status: The HTTP status code returned from the server (will be 3xx). | * status: The HTTP status code returned from the server (will be 3xx). | ||
* notifyData: The plugin's private request data. | * notifyData: The plugin's private request data. | ||
== Response == | == Response == | ||
| Line 57: | Line 51: | ||
== Querying for Support == | == Querying for Support == | ||
The browser will look for 'NPP_URLRedirectNotify' only if the plugin function structure's version field is set to the following value or higher: | |||
NPVERS_HAS_URL_REDIRECT_HANDLER = 26 | |||
The slot for this handler in the plugin function structure can be 'NULL'. If this handler is not provided then redirect behavior is up to the browser. The recommended default behavior is to allow all same-origin redirects and disallow all cross-origin redirects. | |||
Plugins can query the browser for support for this specification by examining the browser's function table. If the version number is equal to or higher than 'NPVERS_HAS_URL_REDIRECT_HANDLER' and the slot for 'NPN_URLRedirectResponse' is non-NULL then the browser will call 'NPP_URLRedirectNotify' when appropriate. | Plugins can query the browser for support for this specification by examining the browser's function table. If the version number is equal to or higher than 'NPVERS_HAS_URL_REDIRECT_HANDLER' and the slot for 'NPN_URLRedirectResponse' is non-NULL then the browser will call 'NPP_URLRedirectNotify' when appropriate. | ||