Closed
Bug 464257
Opened 18 years ago
Closed 18 years ago
enhancement to record (decrypted) transcript of protocol level communication
Categories
(Firefox :: General, enhancement)
Firefox
General
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: don-temp288, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20071126 Fedora/1.5.0.12-7.fc6 Firefox/1.5.0.12
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20071126 Fedora/1.5.0.12-7.fc6 Firefox/1.5.0.12
I'm not sure where to send this request, and the feature might even already exist, but (1)I can't find it, (2)I want a reply (so suggestions won't do), (3)I may be interested in doing the work myself, but will want some advice about how to go about it.
The idea is that for debugging or figuring out what a server is doing, it would be useful for the browser to record a transcript of its communication, including multiple tcp streams. This could sort of be done by a packet sniffer except that it can't deal with encryption, so of course I'd like to tap into the decrypted streams.
So the first question: does this already exist? If so, how do I use it?
If not, is it the sort of thing that you are likely to do soon? And if not, can you offer advice for me if I want to try to do it myself?
And if I send such a facility, do you think you're likely to add it to the code base?
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•18 years ago
|
||
The first thing is that Firefox doesn't do any networking, Gecko is doing that.
You can create a http log http://www.mozilla.org/projects/netlib/http/http-debugging.html
If you want to do that in an addon you should look at livehttpheaders, Firebug or just https://developer.mozilla.org/En
That means it's possible marking wfm
Bugzilla isn't the right place to answer how to use it or how to implement it. Use the Newsgroups or irc or the online Documentation.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
(In reply to comment #1)
> The first thing is that Firefox doesn't do any networking, Gecko is doing
that.
Is Gecko also doing the encryption?
Is there some place I should start reading about the internal structure?
Perhaps that's https://developer.mozilla.org/En
> You can create a http log
> http://www.mozilla.org/projects/netlib/http/http-debugging.html
I notice that this is rather old - the nightly build link brings me to files dated 2005. Perhaps there's something newer?
However, I did grab one of those nightly build files, install it, run it, and generate a log, as the page describes.
It's not quite clear to me how to interpret the log - is there doc on that?
(Probably the answer is to read the code, I realize.)
More important, I don't see all that I hoped to see in that log.
In particular, I expected to see things like this (extracted from tcpdump output but reformatted somewhat by the html form)
POST /aa/reservation/searchFlightsSubmit.do;jsessionid=KNMGXWBHDSLLJEAJJNJSKIEQBFFUWVMD HTTP/1.1
Host: www.aa.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20071126 Fedora/1.5.0.12-7.fc6 Firefox/1.5.0.12
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://www.aa.com/aa/homePage.do
Content-Type: application/x-www-form-urlencoded
Content-Length: 834
currentCodeForm=¤tCalForm=dep&dateChanged=false&fromSearchPage=true&advancedSearchOpened=false&tripType=oneWay&aairpassSearchType=false&originAirport=lax&flightParams.flightDateParams.travelMonth=11&flightParams.flightDateParams.travelDay=27&flightParams.flightDateParams.searchTime=090001&destinationAirport=pit&returnDate.travelMonth=-1000&returnDate.travelDay=-1000&returnDate.searchTime=1530&alternateAirportDistance=0&passengerCount=1&discountCode=&awardDatesFlexible=true&searchTypeMode=schedule&_button_success=GO&adultPassengerCount=1&seniorPassengerCount=0&childPassengerCount=0&infantPassengerCount=0&numberOfStops=P&awardCabinClass=E&classOfServicePreference=coach-restricted&cabinOfServicePreference=matrix-show_all&countryPointOfSaleVal=US&numberOfFlightsToDisplay=10&carrierPreference=T&awardType=M&searchCategory=
I see evidence of the header lines, but not, for example, of the post data, which seems an important part of the protocol level data that I want to capture.
> If you want to do that in an addon you should look at livehttpheaders, Firebug
> or just https://developer.mozilla.org/En
I'm now looking there (thanks for the link), but have little idea of how to find
what I'm looking for.
> That means it's possible marking wfm
> Bugzilla isn't the right place to answer how to use it or how to implement it.
> Use the Newsgroups or irc or the online Documentation.
I hope you don't think that I should read everything there and a substantial
portion of the source in order to answer a question like this!
Your response above would have saved me an enormous amount of effort if that link were really what I wanted. Perhaps the code that generates that transcript can still do what I want with some other options not described in that link. Can you give me an idea of where to look for that code? Or other related code?
For instance, how did you find the link to http-debugging?
Comment 3•17 years ago
|
||
This is my second try because of a crash of my nightly build, it will be shorter then the first try...
Note: I'm not a developer and can not answer questions to the code.
In general:
I would use the Mozilla newsgroups, IRC (try #extdev) or read the code of some addons.
>Is Gecko also doing the encryption?
PSm which is part of Gecko
http://www.mozilla.org/projects/security/pki/psm/
>I notice that this is rather old - the nightly build link brings me to files
>dated 2005. Perhaps there's something newer?
The doc is old but still valid because networking didn't change much but you can only get the headers. You don't need such an old build, you can use every build from 2005 to now which includes every Firefox Release.
There are several addons that use a different API to get the headers:
livehttpheaders, Firebug or https://addons.mozilla.org/en-US/firefox/addon/966.
The last one looks really interesting to me.
If the existing API isn't enough you can write a new bug for extending it but you should study the existing API befire doing that.
I know that i couldn't point you directly to something that you need but the reason is that i don't do extension developing or Gecko developing.
>For instance, how did you find the link to http-debugging?
with google: "Mozilla http log" :-)
I'm triaging 8 years and getting a http log is part of the information that is sometimes needed.
You need to log in
before you can comment on or make changes to this bug.
Description
•