Using the Google Calendar documentation as a reference, I can retrieve and display calendar events like this, where PUBLIC_FEED_URL holds the event feed URL.ĬalendarService myService = new CalendarService("exampleCo-fiddlerExample-1") ĬalendarEventFeed resultFeed = myService.getFeed(feedUrl, CalendarEventFeed.class) ( Editor's Note: as of v3, Google Calendar API no longer uses the Google Data format.) The first thing to do is to get the calendar's event feed URL by clicking on the button on the calendar settings page: The Google Calendar API documentation has information about how to use the RESTful Google Data API to interact with my calendar programmatically. ("All events on your calendar:") įor each packet that matches the filter expression, tcpdump will display a timestamp, the source and destination of the packet, and several TCP flags. This information can be valueable because it shows the order that packets were sent and received. It is often useful to see the contents of the packets as well. The graph, as shown in Figure 6, depicts the result of the HTTP responses (delta time).The '-A' flag tells tcpdump to print each packet in ASCII, exposing the HTTP headers and message body. Step 7: In order to display only the HTTP response, add a filter http.time >=0.0500 in the display filter. Step 6: To calculate the delta (delay) time between request and response, use Time Reference ( CTRL-T in the GUI) for easy delta time calculation. > I/O graph Figure 6: Visualisation of HTTP responses Syntax: http.time >= 0.050000 Figure 5: Statistics. Step 5: Create a filter based on the response time as shown in Figure 4, and visualise the HTTP responses using an I/O graph as shown in Figure 5. Procedure: Right-click on any HTTP response packet -> Protocol preference -> uncheck ‘Reassemble HTTP headers spanning multiple TCP segments’ and ‘Reassemble HTTP bodies spanning multiple TCP segments’.If ‘Allow sub-dissector to reassemble TCP streams’ is on and the HTTP reassembly preferences have been left at their defaults (on), http.time will be the time between the GET request and the last packet of the response.If the TCP preference ‘Allow sub-dissector to reassemble TCP streams’ is off, the http.time will be the time between the GET request and the first packet of the response, the one containing ‘OK’.Go to Protocol preference and then uncheck the sub-dissector to reassemble TCP streams (marked and shown in Figure 3). Step 4: In order to view the response of HTTP, right-click on any response packet (HTTP/1.1). Syntax: ip.addr= 91.198.174.192 & ip.addr = 192.168.155.59 Figure 3: Allow sub-dissector to reassemble TCP streams Figure 4: Response time Start filtering the IP of (a simple traceroute or pathping can reveal the IP address of any Web server) and your local PC IP (a simple ipconfig for Windows and ifconfig for Linux can reveal your local PC IP). Step 3: We now filter the requests and response sent from the local PC to Wikipedia and vice versa. Now filter all the HTTP packets as shown in Figure 2, as follows: syntax: http ‘200 OK’ implies that the response contains a payload, which represents the status of the requested resource (the request is successful). Step 2: Here, we make a request to and, as a result, Wikipedia sends an HTTP response of ‘200 OK’, which indicates the requested action was successful. Figure 1: Interface selection Figure 2: Filtering HTTP
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |