{"action":"created","issue":{"url":"https://api.github.com/repos/IBM-Swift/Kitura-net/issues/68","repository_url":"https://api.github.com/repos/IBM-Swift/Kitura-net","labels_url":"https://api.github.com/repos/IBM-Swift/Kitura-net/issues/68/labels{/name}","comments_url":"https://api.github.com/repos/IBM-Swift/Kitura-net/issues/68/comments","events_url":"https://api.github.com/repos/IBM-Swift/Kitura-net/issues/68/events","html_url":"https://github.com/IBM-Swift/Kitura-net/issues/68","id":170759948,"number":68,"title":"POST command fails with updates from PR 54","user":{"login":"dsperling","id":7662738,"avatar_url":"https://avatars.githubusercontent.com/u/7662738?v=3","gravatar_id":"","url":"https://api.github.com/users/dsperling","html_url":"https://github.com/dsperling","followers_url":"https://api.github.com/users/dsperling/followers","following_url":"https://api.github.com/users/dsperling/following{/other_user}","gists_url":"https://api.github.com/users/dsperling/gists{/gist_id}","starred_url":"https://api.github.com/users/dsperling/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dsperling/subscriptions","organizations_url":"https://api.github.com/users/dsperling/orgs","repos_url":"https://api.github.com/users/dsperling/repos","events_url":"https://api.github.com/users/dsperling/events{/privacy}","received_events_url":"https://api.github.com/users/dsperling/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/IBM-Swift/Kitura-net/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-08-11T22:13:34Z","updated_at":"2016-08-12T15:18:30Z","closed_at":null,"body":"PR https://github.com/IBM-Swift/Kitura-net/pull/54 added a \"Connection: close\" header, which cases certain POST commands using HTTP.request() to fail.\r\n\r\nHere is the verbose output from CURL when used with HTTP.request().\r\n```\r\n*   Trying 10.0.0.1...\r\n* Connected to a.example.com (10.0.0.1) port 443 (#0)\r\n* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256\r\n* Server certificate: *.example.com\r\n> POST /exampleapi HTTP/1.1\r\nHost: a.example.com\r\nAccept: */*\r\nContent-Type: application/json\r\nConnection: close\r\nContent-Length: 39624\r\nExpect: 100-continue\r\n\r\n* Done waiting for 100-continue\r\n* We are completely uploaded and fine\r\n< HTTP/1.1 200 OK\r\n< Content-Type: application/json; charset=UTF-8\r\n< Vary: X-Origin\r\n< Vary: Referer\r\n< Date: Thu, 11 Aug 2016 21:14:20 GMT\r\n< Server: ESF\r\n...\r\n< Accept-Ranges: none\r\n< Vary: Origin,Accept-Encoding\r\n< Connection: close\r\n< \r\n* SSLRead() return error -9806\r\n* Closing connection 0\r\n```\r\n\r\nCommenting out line 290 of ClientRequest.swift allows HTTP POST requests to work.\r\n`//headers[\"Connection\"] = \"close\"`\r\n\r\nTo make the KituraNet HTTP class more general purpose, adding the \"Connection: close\" header should be optional."},"comment":{"url":"https://api.github.com/repos/IBM-Swift/Kitura-net/issues/comments/239475030","html_url":"https://github.com/IBM-Swift/Kitura-net/issues/68#issuecomment-239475030","issue_url":"https://api.github.com/repos/IBM-Swift/Kitura-net/issues/68","id":239475030,"user":{"login":"collinhundley","id":9559558,"avatar_url":"https://avatars.githubusercontent.com/u/9559558?v=3","gravatar_id":"","url":"https://api.github.com/users/collinhundley","html_url":"https://github.com/collinhundley","followers_url":"https://api.github.com/users/collinhundley/followers","following_url":"https://api.github.com/users/collinhundley/following{/other_user}","gists_url":"https://api.github.com/users/collinhundley/gists{/gist_id}","starred_url":"https://api.github.com/users/collinhundley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/collinhundley/subscriptions","organizations_url":"https://api.github.com/users/collinhundley/orgs","repos_url":"https://api.github.com/users/collinhundley/repos","events_url":"https://api.github.com/users/collinhundley/events{/privacy}","received_events_url":"https://api.github.com/users/collinhundley/received_events","type":"User","site_admin":false},"created_at":"2016-08-12T15:18:30Z","updated_at":"2016-08-12T15:18:30Z","body":"@shmuelk Hmm, I wonder why it's causing issues with SSL on certain sites. In my case the issue occurs when accessing the Google Maps API (see #69). Is it possible that it's not following a redirect properly, or something like that? "}}
{"actor":{"display_login":"collinhundley"}}