ipv6 support for the web-server
See original GitHub issueOur internal Docker-based web-service allows to run other web-services only as listening to ipv6. Can you please help me how to achieve this?
I use web/Docker with the minor diff:
CMD ["CodeChecker", "server", "--workspace", "/workspace", "--not-host-only", "--port", "8080", "--verbose", "debug"]
I have no ideas for ipv6 except for
- client_host, client_port = self.client_address
+ client_host, client_port = self.client_address[:2]
and
daemon_threads = False
+ address_family = socket.AF_INET6
It helps but Thrift wrapper in JS fails to get the product list:
Uncaught Thrift.TApplicationExceptioncode: 6message: “Bad data encounted in numeric data” codeCheckerDBAccess.js:7166
It’s
codeCheckerDBAccess_v6.codeCheckerDBAccessClient.prototype.recv_getRunData = function() {
var ret = this.input.readMessageBegin();
var fname = ret.fname;
var mtype = ret.mtype;
var rseqid = ret.rseqid;
if (mtype == Thrift.MessageType.EXCEPTION) {
var x = new Thrift.TApplicationException();
x.read(this.input);
this.input.readMessageEnd();
throw x; // <--------------- line 7166
}
Callstack looks like
codeCheckerDBAccess_v6.codeCheckerDBAccessClient.recv_getRunData (codeCheckerDBAccess.js:7166)
codeCheckerDBAccess_v6.codeCheckerDBAccessClient.getRunData (codeCheckerDBAccess.js:7135)
_populateRuns (ListOfRuns.js:299)
postCreate (ListOfRuns.js:188)
create (_WidgetBase.js:84)
postscript (_WidgetBase.js:50)
(anonymous) (dojo.js:15)
postCreate (ListOfRuns.js:466)
create (_WidgetBase.js:84)
postscript (_WidgetBase.js:50)
I have no ideas what to check next. Can you please advice me?
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
IPv6 and Apache Web Server - HPCpublic - HPCMP
The Apache web server has had Internet Protocol version 6 (IPv6) support built in and enabled by default since 2002 (with the release...
Read more >Should You Care About IPv6 Connectivity For Your Web Server?
Before you begin, you'll need to make sure your web server is even accessible over IPv6. This will usually involve you requesting an...
Read more >How to prepare your webserver for IPV6 - edpnet.be
Nowadays all the modern system operatives come with IPv6 support, but you need to enable and configure the IPv6 addresses for each part...
Read more >How to Enable IPv6 in Nginx & Apache? - Geekflare
Let's see the procedure to implement IPv6 in Apache HTTP and the Nginx web server. How to find IPv6 on Linux? Before enabling...
Read more >8 steps to get your site ready for IPv6 - ARIN
1. Add an IPv6 address to your web server · 2. Add an AAAA record for your website · 3. Add an AAAA...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@irishrover I do not think it was the cookies, but rather the JavaScript stuff being cached, as per detailed in #2228. Anyways, thanks for the report, with the patch being merged I hope we can officially support a proper IPv6 binding. Until then, yeah, setting the
address_family
is the crucial part of the hack.@Xazax-hun Starting from Python 3.8, simply giving an IPv6 address to the server (
--host ::1
) would make it listen IPv6.I’m making a patch for 3.6 and 3.7 (@gyorb said we require 3.6), and there’s a few more nits here and there to make sure everything works as intended.