javascript - Firefox-Identifica quién inició la solicitud http

firefox-addon firefox-addon-sdk

Question

En mi complemento actual, intercepto todas las solicitudes http en firefox con http-on-modify-request

En realidad, con mi código actual puedo separar las solicitudes provenientes de las páginas web / pestañas y todo el resto (por ejemplo, actualizaciones de fuentes RSS, solicitudes del administrador de extensiones, solicitudes XHR de componentes XPCOM, etc.)

Me gustaría identificar quién inicia una solicitud aparte del tráfico web con precisión, no solo para todo el grupo (actualizaciones de fuentes RSS, solicitudes del administrador de extensiones, solicitudes XHR de componentes XPCOM, etc.).

Ejemplo: una variable personalizada requestRequestor tendría un valor para identificar un complemento específico o una actualización de RSS, etc.

Yo formulé esta pregunta silimar Identificar solicitudes provenientes de PageWorker sin una solución.

El código actual para identificar a todo el grupo ( obtener el navegador que activa la notificación http-on-modify-request ) es similar a:

Components.utils.import(''resource://gre/modules/Services.jsm'');
Services.obs.addObserver(httpObs, ''http-on-modify-request'', false);
//Services.obs.removeObserver(httpObs, ''http-on-modify-request''); //uncomment this line, or run this line when you want to remove the observer
var httpObs = {
observe: function (aSubject, aTopic, aData) {
if (aTopic == ''http-on-modify-request'') {
/*start - do not edit here*/
var oHttp = aSubject.QueryInterface(Components.interfaces.nsIHttpChannel); //i used nsIHttpChannel but i guess you can use nsIChannel, im not sure why though
var interfaceRequestor = oHttp.notificationCallbacks.QueryInterface(Components.interfaces.nsIInterfaceRequestor);
//var DOMWindow = interfaceRequestor.getInterface(Components.interfaces.nsIDOMWindow); //not to be done anymore because: https://developer.mozilla.org/en-US/docs/Updating_extensions_for_Firefox_3.5#Getting_a_load_context_from_a_request //instead do the loadContext stuff below
var loadContext;
try {
loadContext = interfaceRequestor.getInterface(Components.interfaces.nsILoadContext);
} catch (ex) {
try {
loadContext = aSubject.loadGroup.notificationCallbacks.getInterface(Components.interfaces.nsILoadContext);
//in ff26 aSubject.loadGroup.notificationCallbacks was null for me, i couldnt find a situation where it wasnt null, but whenever this was null, and i knew a loadContext is supposed to be there, i found that "interfaceRequestor.getInterface(Components.interfaces.nsILoadContext);" worked fine, so im thinking in ff26 it doesnt use aSubject.loadGroup.notificationCallbacks anymore, but im not sure
} catch (ex2) {
loadContext = null;
//this is a problem i dont know why it would get here
}
}
/*end do not edit here*/
/*start - do all your edits below here*/
var url = oHttp.URI.spec; //can get url without needing loadContext
if (loadContext) {
var contentWindow = loadContext.associatedWindow; //this is the HTML window of the page that just loaded
//aDOMWindow this is the firefox window holding the tab
var aDOMWindow = contentWindow.top.QueryInterface(Ci.nsIInterfaceRequestor).getInterface(Ci.nsIWebNavigation).QueryInterface(Ci.nsIDocShellTreeItem).rootTreeItem.QueryInterface(Ci.nsIInterfaceRequestor).getInterface(Ci.nsIDOMWindow);
var gBrowser = aDOMWindow.gBrowser; //this is the gBrowser object of the firefox window this tab is in
var aTab = gBrowser._getTabForContentWindow(contentWindow.top); //this is the clickable tab xul element, the one found in the tab strip of the firefox window, aTab.linkedBrowser is same as browser var above //can stylize tab like aTab.style.backgroundColor = ''blue''; //can stylize the tab like aTab.style.fontColor = ''red'';
var browser = aTab.linkedBrowser; //this is the browser within the tab //this is what the example in the previous section gives
//end getting other useful stuff
} else {
Components.utils.reportError(''EXCEPTION: Load Context Not Found!!'');
//this is likely no big deal as the channel proably has no associated window, ie: the channel was loading some resource. but if its an ajax call you may end up here
}
}
}
};

Gracias por tu tiempo

Answer 1

Necesitas mirar al AGENTE DE USUARIO dentro del encabezado HTTP. Proporciona detalles sobre el sistema del cliente.

espero que esto ayude:

https://msdn.microsoft.com/en-us/library/ms537503(v=vs.85).aspx (que comprende la cadena de agente de usuario),

http://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_nav_all (ejemplo de agente de usuario)

PD: Quería publicarlo como un comentario pero no vi la opción.