| 8 | | It's possible to build the HTTP library in debug mode, and in that case it will trace all operations it performs to standard output. This could give some infos on what is happening, maybe? |
| | 8 | It's possible to build the HTTP library in debug mode, and in that case it will trace all operations it performs to standard output. This does not reveal any problem with parsing the headers: |
| | 9 | |
| | 10 | {{{ |
| | 11 | HTTPS: Resolving https://ir-na.amazon-adsystem.com/e/ir?l=w41&t=thedigitalt02-202&o=1&cb=1501216857775 |
| | 12 | HTTPS: Hostname resolved to: 176.32.96.208:443 |
| | 13 | HTTPS: Connection to ir-na.amazon-adsystem.com on port 443. |
| | 14 | HTTPS: Connection opened, sending request. |
| | 15 | --> HTTPS: Host: ir-na.amazon-adsystem.com |
| | 16 | --> HTTPS: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 |
| | 17 | --> HTTPS: Accept-Encoding: gzip |
| | 18 | --> HTTPS: Connection: close |
| | 19 | --> HTTPS: User-Agent: Mozilla/5.0 (Macintosh; Intel Haiku R1 x86) AppleWebKit/602.1.19 (KHTML, like Gecko) WebPositive/1.2 Version/8.0 Safari/602.1.19 |
| | 20 | HTTPS: Request sent. |
| | 21 | HTTPS: Status line received: Code 200 () |
| | 22 | <-- HTTPS: Content-Type: image/gif |
| | 23 | <-- HTTPS: Connection: close |
| | 24 | <-- HTTPS: Content-Length: 42 |
| | 25 | <-- HTTPS: Cache-Control: no-cache |
| | 26 | <-- HTTPS: Pragma: no-cache |
| | 27 | HTTPS: 5 headers and 0 bytes of data remaining |
| | 28 | }}} |
| | 29 | |
| | 30 | (unless I'm not served the page from the same server and only some servers have the problem?) |
