I’m currently at work stressed too and I don’t know, when I have time on weekend.
So take your time for the analysis
I tried it without the false flagged station, but the problem persists.
Maybe it makes sense, that I give you remote access to my Pi. I’ll explore the possibilities for that and I’ll contact you for that via PM.
Thanks and have a nice weekend
In case you have time please give following information:
Version used (OH stable release 2.1 or snapshot release 2.2)
Do all stations change to online? If not please provide the log readout for that station which gives the full web-return.
Please post the web-return of all stations before the error. (Probably a single return as posted above).
Do delete your API key in all cases.
Using those web-returns I should be able to get your observed error. That way no direct connection to your system is needed.
In the log the returns from Tankerkoenig are included if DEBUG level is set.
If all the Stations remain OFFLINE there is probably only one return for each station.
I have made some changes to the binding already, which are in the Snapshot release. Those changes did also cover if a Station does not give all the prices, since you are getting an error even without the station reporting no E10 price, that might not help.
You do not need to change to the full snapshot release (2.2), by deinstalling the binding via PaperUI and placing only the updated binding into the addons folder you would use the new one.
How I can find the updated binding? Did you have a link? I can find only the OH2.2 distro on Github.
You should be able to download it from here.
After you have deinstalled via PaperUI and installed the new version by putting it into the addons folder you can check wether the correct one is used on the Karaf console. Use “bundle:list” to show all addons, there should only be one Tankerkoening binding listed, with version 2.2.0 followed by a DateTimeGroup.
After installing you need to delete all (Tankerkoenig)things created with the old binding and reinsert them! (Otherwise they will not use the complete new code).
If you have successfully installed the new binding and see errors again, please post the logs (without API-keys) else…
New version installed and active (I see it via bundle:list), but not happens. Here is the log from startup (only tankerkoenig messages).
pi@pi:/opt/openHAB2 $ ./start_debug.sh
Launching the openHAB runtime…
Listening for transport dt_socket at address: 5005
__ _____ ____
____ ____ ___ ____ / / / / | / __ )
/ __ / __ / _ / __ / // / /| | / __ |
/ // / // / __/ / / / __ / ___ |/ // /
_/ ./_// /// /// |/_____/
/_/ 2.1.0
- release build -
Hit ‘’ for a list of available commands
and ‘[cmd] --help’ for help on a specific command.
Hit ‘’ or type ‘system:shutdown’ or ‘logout’ to shutdown openHAB.
openhab> log:tail
10:55:20.678 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link ‘E10_JetFreiberg-tankerkoenig:station:WebserviceName:StationJetFreiberg:e10’ has been added.
10:55:21.401 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'tankerkoenig.things’
10:56:19.117 [DEBUG] [org.openhab.binding.tankerkoenig ] - BundleEvent STARTING - org.openhab.binding.tankerkoenig
10:56:19.130 [DEBUG] [org.openhab.binding.tankerkoenig ] - BundleEvent STARTED - org.openhab.binding.tankerkoenig
10:56:19.146 [DEBUG] [org.openhab.binding.tankerkoenig ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=binding.tankerkoenig, component.id=216, service.id=342, service.bundleid=223, service.scope=bundle} - org.openhab.binding.tankerkoenig
10:56:20.981 [INFO ] [smarthome.event.ThingAddedEvent ] - Thing ‘tankerkoenig:webservice:WebserviceName’ has been added.
10:56:21.054 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘tankerkoenig:webservice:WebserviceName’ changed from UNINITIALIZED to INITIALIZING
10:56:21.055 [DEBUG] [nkerkoenig.handler.WebserviceHandler] - Initialize Bridge
10:56:21.069 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘tankerkoenig:webservice:WebserviceName’ changed from INITIALIZING to UNKNOWN
10:56:21.076 [DEBUG] [nkerkoenig.handler.WebserviceHandler] - Refresh job scheduled to run every 10 min. for 'tankerkoenig:webservice:WebserviceName’
10:56:21.086 [INFO ] [smarthome.event.ThingAddedEvent ] - Thing ‘tankerkoenig:station:WebserviceName:StationJetFreiberg’ has been added.
10:56:21.105 [DEBUG] [.tankerkoenig.handler.StationHandler] - Initializing Tankerkoenig handler 'tankerkoenig:station:WebserviceName:StationJetFreiberg’
10:56:21.105 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘tankerkoenig:station:WebserviceName:StationJetFreiberg’ changed from UNINITIALIZED to INITIALIZING
10:56:21.117 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘tankerkoenig:station:WebserviceName:StationJetFreiberg’ changed from INITIALIZING to UNKNOWN
10:56:21.126 [DEBUG] [.tankerkoenig.handler.StationHandler] - Refresh job scheduled to run every 24 hours for 'tankerkoenig:station:WebserviceName:StationJetFreiberg’
10:56:36.126 [DEBUG] [.tankerkoenig.handler.StationHandler] - Try to refresh detail data
10:56:36.395 [DEBUG] [lipse.smarthome.io.net.http.HttpUtil] - About to execute https://creativecommons.tankerkoenig.de/json/detail.php?id=51d4b529-a095-1aa0-e100-80009459e03a&apikey=[Removed]
10:56:37.335 [DEBUG] [ig.internal.data.TankerkoenigService] - getTankerkoenigDetailResult IOException:
java.io.IOException: java.util.concurrent.TimeoutException
at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrlAndGetReponse(HttpUtil.java:255)[113:org.eclipse.smarthome.io.net:0.9.0.b5]
at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrl(HttpUtil.java:149)[113:org.eclipse.smarthome.io.net:0.9.0.b5]
at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrl(HttpUtil.java:122)[113:org.eclipse.smarthome.io.net:0.9.0.b5]
at org.openhab.binding.tankerkoenig.internal.data.TankerkoenigService.getResponseString(TankerkoenigService.java:67)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at org.openhab.binding.tankerkoenig.internal.data.TankerkoenigService.getTankerkoenigDetailResult(TankerkoenigService.java:90)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at org.openhab.binding.tankerkoenig.internal.data.TankerkoenigService.getStationDetailData(TankerkoenigService.java:48)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at org.openhab.binding.tankerkoenig.handler.StationHandler.updateDetailData(StationHandler.java:156)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at org.openhab.binding.tankerkoenig.handler.StationHandler$1.run(StationHandler.java:94)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
Caused by: java.util.concurrent.TimeoutException
at org.eclipse.jetty.client.util.FutureResponseListener.get(FutureResponseListener.java:109)[68:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:655)[68:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrlAndGetReponse(HttpUtil.java:246)[113:org.eclipse.smarthome.io.net:0.9.0.b5]
… 14 more
10:56:37.375 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘tankerkoenig:station:WebserviceName:StationJetFreiberg’ changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): No valid response from the web-request!
OK.
Just got make sure, did you copy the full request (the one from which removed the API key) from the log into the browser and get a valid response? I apologise for that question, but when searching for errors you got that be sure of every step.
If that is true,please request a log-file from Tankerkoenig.de (under https://creativecommons.tankerkoenig.de menu item Tools) and verify if the requests of the binding did go to them at all.
The reason I’m searching primarily in that direction is that others do not report such failure!
I check to log file from Tankerkoenig.de and I see, that the request of the binding is not received by the server. In my opinion, that fact match with the timeout message. I see only my test requests from the browser. Note: I used the Epiphany browser direct under the Pi Desk.
[MyExternalIP-Removed] - - [06/Nov/2017:14:55:56 +0100] “GET /json/detail.php?id=51d4b529-a095-1aa0-e100-80009459e03a&apikey=[Removed] HTTP/1.1” 200 417 “-” “Mozilla/5.0 (Macintosh; ARM Mac OS X) AppleWebKit/538.15 (KHTML, like Gecko) Safari/538.15 Version/6.0 Raspbian/8.0 (1:3.8.2.0-0rpi27rpi1g) Epiphany/3.8.2” 0.007
Sometimes I get another exception with the same negative result:
15:18:59.032 [DEBUG] [ig.internal.data.TankerkoenigService] - getTankerkoenigDetailResult IOException:
java.io.IOException: java.util.concurrent.ExecutionException: java.nio.channels.ClosedChannelException
at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrlAndGetReponse(HttpUtil.java:255)[113:org.eclipse.smarthome.io.net:0.9.0.b5]
at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrl(HttpUtil.java:149)[113:org.eclipse.smarthome.io.net:0.9.0.b5]
at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrl(HttpUtil.java:122)[113:org.eclipse.smarthome.io.net:0.9.0.b5]
at org.openhab.binding.tankerkoenig.internal.data.TankerkoenigService.getResponseString(TankerkoenigService.java:67)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at org.openhab.binding.tankerkoenig.internal.data.TankerkoenigService.getTankerkoenigDetailResult(TankerkoenigService.java:90)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at org.openhab.binding.tankerkoenig.internal.data.TankerkoenigService.getStationDetailData(TankerkoenigService.java:48)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at org.openhab.binding.tankerkoenig.handler.StationHandler.updateDetailData(StationHandler.java:156)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at org.openhab.binding.tankerkoenig.handler.StationHandler$1.run(StationHandler.java:94)[223:org.openhab.binding.tankerkoenig:2.2.0.201711051935]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
Caused by: java.util.concurrent.ExecutionException: java.nio.channels.ClosedChannelException
at org.eclipse.jetty.client.util.FutureResponseListener.getResult(FutureResponseListener.java:118)[68:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.util.FutureResponseListener.get(FutureResponseListener.java:110)[68:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:655)[68:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrlAndGetReponse(HttpUtil.java:246)[113:org.eclipse.smarthome.io.net:0.9.0.b5]
… 14 more
Caused by: java.nio.channels.ClosedChannelException
at org.eclipse.jetty.io.WriteFlusher.onClose(WriteFlusher.java:482)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.io.AbstractEndPoint.onClose(AbstractEndPoint.java:109)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.io.AbstractEndPoint.close(AbstractEndPoint.java:116)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.close(SslConnection.java:913)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:667)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.flush(SslConnection.java:841)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:408)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:364)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.io.ssl.SslConnection$1.run(SslConnection.java:98)[71:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[83:org.eclipse.jetty.util:9.2.19.v20160908]
… 1 more
Now I looked at your problem using a real computer.
Sorry for asking for a “web-return” out of your logs, since you never got a web-return using the binding, you couldn’t give that!
The two different Errors both point to the same problem: The request sent to Tankerkoenig timed out! The timeout is set to 5000 (i.e. 5 seconds). I’ll send you a version with a 20 second timeout, please try that. If it works, we can try to adjust a smaller timeout, if not…
Since the changed binding didn’t help, are you by chance using any other binding that does web-requests?
Currently not. I don’t know, which available bindings are using web requests.
As an example the Weatherunderground binding is using the HttpUtil as well.
Note that I do assume that this binding would have the same error.
I’m trying to get some other opinions on your problem, but got no answer yet.
Wunderground binding installed and it’s running fine (Sorry for that bad news).
228 | Active | 80 | 2.2.0.201711062100 | Tankerkoenig Binding
230 | Active | 80 | 0.9.0.201703181903 | WeatherUnderground Binding
08:09:13.919 [INFO ] [marthome.event.ItemStateChangedEvent] - WUConditions changed from NULL to Overcast
08:09:13.953 [INFO ] [marthome.event.ItemStateChangedEvent] - WUObservationTime changed from NULL to 2017-11-09T07:57:29.000+0100
08:09:13.966 [INFO ] [marthome.event.ItemStateChangedEvent] - WUObservationLocation changed from NULL to Straße zum Forst, Halsbrücke,
08:09:13.985 [INFO ] [marthome.event.ItemStateChangedEvent] - WUStation changed from NULL to IHALSBRC2
08:09:14.000 [INFO ] [marthome.event.ItemStateChangedEvent] - WUTemperature changed from NULL to 4.9
08:09:14.027 [INFO ] [marthome.event.ItemStateChangedEvent] - WUFeelTemp changed from NULL to 5
08:09:14.058 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'wunderground.items’
08:09:14.059 [INFO ] [marthome.event.ItemStateChangedEvent] - WUHumidity changed from NULL to 97
08:09:14.085 [INFO ] [marthome.event.ItemStateChangedEvent] - WUPressure changed from NULL to 1020
08:17:48.172 [INFO ] [marthome.event.ItemStateChangedEvent] - WUObservationTime changed from 2017-11-09T07:57:29.000+0100 to 2017-11-09T08:08:40.000+0100
08:32:47.160 [DEBUG] [nd.handler.WeatherUndergroundHandler] - URL = http://api.wunderground.com/api/[REMOVED]/conditions/forecast10day/lang:DE/q/50.95868301,13.43252182.json
08:32:47.751 [DEBUG] [nd.handler.WeatherUndergroundHandler] - weatherData =
{
“response”: {
“version”:“0.1”,
“termsofService”:“http://www.wunderground.com/weather/api/d/terms.html”,
“features”: {
“conditions”: 1
,
“forecast10day”: 1
}
}
, “current_observation”: {
“image”: {
“url”:“http://icons.wxug.com/graphics/wu2/logo_130x80.png”,
“title”:“Weather Underground”,
“link”:“http://www.wunderground.com”
},
…Snip
No other message for Wunderground assigned things/items in the log. I have set debug level for the wunderground binding and handler!
Thanks. Scratching head…Looking…
This was the part of your log from Tankerkoenig. The part in bold makes me wonder! I would have expected something like: HTTP/1.1" 200 266 “-” “Jetty/9.2.19.v20160908” 0.003
79.238.201.187
That states the use of jetty (the webserver of OH). Presently I have no idea why your system isn’t using jetty for the Tankerkoenig web-requests. I would have assumed that the same would happen with the WeaterUndergrounf binding, but as seen this binding is working.
I’ll have a closer look into both codes in order to spot the differences.
You misunderstood me, because I wrote:
I never saw any request from the TK-Binding in the exported TK-Log. The log you quoted is from my test via desktop browser Epiphany direct on the Pi desktop. I wanted to check, that the connection from the Pi to TK is working and I wanted to exclude any connection errors.
OK, Thanks for pointing that out. I was on wrong path.
I had a look already into the WeatherUnderGround code, the main difference (beside the use of another overload of “executeURL”) is a TimeOut of 30 seconds.
I can’t believe that a further extended TimeOut would help, but I’ll give it a try.
I can’t compile from work, so you have to wait until tonight.
Maybe following information can help. I’ve run tcpdump on my Pi, filtered for the IP of creativecommons.tankerkoenig.de. There is only one line and it looks like the DNS response (*.1.99 is my Router, *.1.48 is the Pi):
13:21:21.291450 IP 192.168.1.99.domain > 192.168.1.48.42147: 12092 1/0/0 A 188.68.35.147 (65)
For comparison here the same with dumping all with the IP of api.wunderground.com. The DNS response is a little bit different and I think, your binding dont even try to open a connection and the binding except before.
13:26:45.824582 IP 192.168.1.99.domain > 192.168.1.48.60560: 47231 3/0/0 CNAME api.wunderground.com.edgekey.net., CNAME e12930.g.akamaiedge.net., A 23.53.166.130 (134)
13:26:45.826121 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [S], seq 3497460722, win 29200, options [mss 1460,sackOK,TS val 25244367 ecr 0,nop,wscale 7], length 0
13:26:45.854850 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [S.], seq 3022217929, ack 3497460723, win 28960, options [mss 1460,sackOK,TS val 1122679933 ecr 25244367,nop,wscale 5], length 0
13:26:45.855055 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 1, win 229, options [nop,nop,TS val 25244369 ecr 1122679933], length 0
13:26:45.866506 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [P.], seq 1:244, ack 1, win 229, options [nop,nop,TS val 25244371 ecr 1122679933], length 243: HTTP: GET /api/03800101a14c990f/conditions/forecast10day/lang:DE/q/50.95868301,13.43252182.json HTTP/1.1
13:26:45.907002 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], ack 244, win 939, options [nop,nop,TS val 1122679977 ecr 25244371], length 0
13:26:46.224067 IP 192.168.1.99.domain > 192.168.1.48.38566: 22422 1/0/0 PTR a23-53-166-130.deploy.static.akamaitechnologies.com. (109)
13:26:46.236194 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 1:1449, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP: HTTP/1.1 200 OK
13:26:46.236342 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 1449, win 251, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.236466 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 1449:2897, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.236508 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 2897, win 274, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.236628 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 2897:4345, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.236677 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 4345, win 296, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.236851 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 4345:5793, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.236883 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 5793, win 319, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.237108 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 5793:7241, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.237150 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 7241, win 342, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.237296 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 7241:8689, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.237330 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 8689, win 364, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.238765 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 8689:10137, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.238838 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 10137, win 387, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.239062 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 10137:11585, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.239123 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 11585, win 410, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.239511 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 11585:13033, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP: ": 265
13:26:46.239547 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 13033, win 432, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.239718 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 13033:14481, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.239759 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 14481, win 455, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.239883 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 14481:15929, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.239916 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 15929, win 477, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.240087 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 15929:17377, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.240134 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 17377, win 500, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.240442 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 17377:18825, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.240549 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 18825, win 523, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.240636 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [.], seq 18825:20273, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1448: HTTP
13:26:46.240669 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 20273, win 545, options [nop,nop,TS val 25244408 ecr 1122680313], length 0
13:26:46.248581 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [P.], seq 20273:21636, ack 244, win 939, options [nop,nop,TS val 1122680313 ecr 25244371], length 1363: HTTP
13:26:46.248695 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 21636, win 568, options [nop,nop,TS val 25244409 ecr 1122680313], length 0
13:26:56.275531 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [F.], seq 244, ack 21636, win 568, options [nop,nop,TS val 25245412 ecr 1122680313], length 0
13:26:56.325773 IP a23-53-166-130.deploy.static.akamaitechnologies.com.http > 192.168.1.48.53167: Flags [F.], seq 21636, ack 245, win 939, options [nop,nop,TS val 1122690403 ecr 25245412], length 0
13:26:56.325909 IP 192.168.1.48.53167 > a23-53-166-130.deploy.static.akamaitechnologies.com.http: Flags [.], ack 21637, win 568, options [nop,nop,TS val 25245417 ecr 1122690403], length 0
