https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412008-02-06T16:34:03Zlighty labsLighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=34672008-02-06T16:34:03Zadmin
<ul></ul><blockquote>
<p>Is there a reason why init_aton() is used iso gethostbyname() or getaddrinfo()?</p>
</blockquote>
<p>Maybe because it is non-blocking while the other two are blocking.</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=53092009-02-04T18:40:28Zahknight
<ul></ul><p>We just got bitten by this. The documentation must agree with the implementation.</p>
<p>Please either update the code to work as documented or update the documentation to say that it requires only IPs.</p>
<p>Thanks..</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=62902009-08-15T00:23:52Zschwern
<ul></ul><p>I'd like to add a "me too" here and request this be considered for a 1.4.x patch. Having to use IP addresses has added difficulties to maintaining an application server farm.</p>
<p>lighty + mod_fastcgi made that server farm a lot smaller than it would be with the equivalent Apache setup. :)</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=67362010-01-29T09:58:36ZOlaf-van-der-Spek
<ul><li><strong>Assignee</strong> deleted (<del><i>jan</i></del>)</li><li><strong>Target version</strong> changed from <i>1.5.0</i> to <i>1.4.26</i></li></ul> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=67662010-02-03T21:59:44Zstbuehler
<ul><li><strong>Target version</strong> changed from <i>1.4.26</i> to <i>1.4.27</i></li><li><strong>Missing in 1.5.x</strong> set to <i>No</i></li></ul> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=69002010-04-28T15:07:18Zstbuehler
<ul><li><strong>Target version</strong> changed from <i>1.4.27</i> to <i>1.4.x</i></li></ul><p>I updated the docs so at least they are correct now :)</p>
I think it isn't easy to define a sane behaviour for dns names:
<ul>
<li>resolve ipv4, ipv6?</li>
<li>how handle multiple ips?</li>
<li>ttl of dns names?</li>
</ul> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=69102010-04-29T15:48:34ZOlaf-van-der-Spek
<ul></ul><p>It may not be easy, but is that a reason to not do anything at all?</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=69112010-04-29T15:51:23Zstbuehler
<ul></ul><p>Do it yourself.</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=69722010-05-22T18:22:01ZOlaf-van-der-Spek
<ul></ul><p>stbuehler wrote:</p>
<blockquote>
<p>I updated the docs so at least they are correct now :)</p>
</blockquote>
<p>Are they?</p>
<p><a class="external" href="http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:ConfigurationOptions#mod_fastcgi-fastcgi">http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:ConfigurationOptions#mod_fastcgi-fastcgi</a><br />host is hostname/ip of the FastCGI process <br />host is hostname/ip of the SCGI process</p>
<p>How does mod_proxy do this? I'm sure proxies aren't limited to IP addresses.</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=71262010-07-20T11:40:29ZOlaf-van-der-Spek
<ul><li><strong>Target version</strong> changed from <i>1.4.x</i> to <i>1.4.27</i></li></ul><p>Docs not fixed yet...</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=71522010-08-05T21:18:33Zstbuehler
<ul><li><strong>Category</strong> changed from <i>mod_fastcgi</i> to <i>documentation</i></li><li><strong>Target version</strong> deleted (<del><i>1.4.27</i></del>)</li></ul><p>It is a wiki. Thx for helping :)</p>
<p>lighttpd doesn't do any DNS lookups, so you will always have to use ips.</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=94862016-04-29T08:44:27Zgstrauss
<ul><li><strong>Subject</strong> changed from <i>mod_fastcgi doesn not accept hostnames for 'host'. This is not according to Docs:ModFastCGI</i> to <i>mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGI</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Fixed</i></li></ul><p>I verified that the docs state to use IP address string:</p>
<p><a class="external" href="https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:ConfigurationOptions">https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:ConfigurationOptions</a><br /><a class="external" href="https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModFastCGI">https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModFastCGI</a><br /><a class="external" href="https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModProxy">https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModProxy</a></p>
<p>Yes, mod_fastcgi, mod_scgi, and mod_proxy all require IP address string for host. None use DNS.</p>
<p>musings on supporting DNS:<br />DNS is possibly blocking. 'A' records could point to multiple IPs. Lookups might return both 'A' and 'AAAA' records, or 'CNAME' records. DNS record TTLs might need to be handled. The list goes on. Reliance on DNS, even if done only at startup, might result in apparent hangs if DNS is slow or not responding. I could see the possibility of having a configuration switch to enable use of DNS, so that admin could opt-in to this possibly blocking behavior, and I could see doing DNS lookups only at startup, and only taking the first address returned. Such a feature request might be sufficient to add convenience to the configurations of many -- <em>not all</em> -- usage scenarios. Async DNS is also a possibility, but all of the above is definitely a feature request (or multiple feature requests), and the changes required to implement them might not be appropriate for the 1.4.x branch.</p> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=94872016-04-29T08:44:50Zgstrauss
<ul><li><strong>Target version</strong> set to <i>1.4.x</i></li></ul> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=102282016-07-16T12:41:29Zstbuehler
<ul><li><strong>Target version</strong> deleted (<del><i>1.4.x</i></del>)</li></ul> Lighttpd - Bug #1417: mod_fastcgi doesn't accept hostnames for 'host'. This is not according to Docs:ModFastCGIhttps://redmine.lighttpd.net/issues/1417?journal_id=108722017-02-20T11:54:03ZArchy
<ul></ul><p>Dropping support for lighttpd docker for my application, because of this.</p>