commit c0f773a616fb48bf699539c5ac18bd9c55a540c9
Author: Roman Podoliaka <email address hidden>
Date: Mon Feb 16 11:55:07 2015 +0200
Fix VNC access, when reverse DNS lookups fail
If DNS is configured on a node in a way, so that reverse DNS look ups
time out, noVNC will fail to connect to an instance with 'Connect
timeout' error.
The reverse DNS look up is done implicitly in BaseHTTPRequestHandler
(part of standard library), when logging a request. It's not
configurable, so the only way to disable it is to override the method
of the base class.
This is only true for the standard http server (used for novncproxy),
as the eventlet implementation (used for xvpvncproxy) seems to use
plain IP addresses without any reverse DNS look ups.
Reviewed: https:/ /review. openstack. org/156196 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=c0f773a616f b48bf699539c5ac 18bd9c55a540c9
Committed: https:/
Submitter: Jenkins
Branch: master
commit c0f773a616fb48b f699539c5ac18bd 9c55a540c9
Author: Roman Podoliaka <email address hidden>
Date: Mon Feb 16 11:55:07 2015 +0200
Fix VNC access, when reverse DNS lookups fail
If DNS is configured on a node in a way, so that reverse DNS look ups
time out, noVNC will fail to connect to an instance with 'Connect
timeout' error.
The reverse DNS look up is done implicitly in BaseHTTPRequest Handler
(part of standard library), when logging a request. It's not
configurable, so the only way to disable it is to override the method
of the base class.
This is only true for the standard http server (used for novncproxy),
as the eventlet implementation (used for xvpvncproxy) seems to use
plain IP addresses without any reverse DNS look ups.
Closes-Bug: #1422315
Change-Id: I8b922de49134ed a4d753a8e906b0d e55203877d3