{"push_id":579129698,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"c4a9cc56b2e783f5968c2696377ba8d488ed357d","before":"6b31d0529d82fe542e0cc423fefe0ac86b350c48","commits":[{"sha":"c0f773a616fb48bf699539c5ac18bd9c55a540c9","author":{"email":"e54ac0254958210cc7aaf4795d156f3b6e6ea9e1@mirantis.com","name":"Roman Podoliaka"},"message":"Fix VNC access, when reverse DNS lookups fail\n\nIf DNS is configured on a node in a way, so that reverse DNS look ups\ntime out, noVNC will fail to connect to an instance with 'Connect\ntimeout' error.\n\nThe reverse DNS look up is done implicitly in BaseHTTPRequestHandler\n(part of standard library), when logging a request. It's not\nconfigurable, so the only way to disable it is to override the method\nof the base class.\n\nThis is only true for the standard http server (used for novncproxy),\nas the eventlet implementation (used for xvpvncproxy) seems to use\nplain IP addresses without any reverse DNS look ups.\n\nCloses-Bug: #1422315\n\nChange-Id: I8b922de49134eda4d753a8e906b0de55203877d3","distinct":true,"url":"https://api.github.com/repos/openstack/nova/commits/c0f773a616fb48bf699539c5ac18bd9c55a540c9"},{"sha":"c4a9cc56b2e783f5968c2696377ba8d488ed357d","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Fix VNC access, when reverse DNS lookups fail\"","distinct":true,"url":"https://api.github.com/repos/openstack/nova/commits/c4a9cc56b2e783f5968c2696377ba8d488ed357d"}]}