public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* latest lighttpd (1.4.45) not working on Windows 10 Home Edition
@ 2018-11-29 14:31 Alejandro Benitez
  2018-12-07 14:14 ` Alejandro Benitez
  0 siblings, 1 reply; 4+ messages in thread
From: Alejandro Benitez @ 2018-11-29 14:31 UTC (permalink / raw)
  To: cygwin

Hi,
Id like to share that the latest Cygwin lighttpd package does not work 
for me on Windows 10 Home Edition. Neither 32-bit nor 64-bit package. I 
had the chance to test it on both architectures because when I first ran 
into this problem I was running Windows 10 32-bit on this AMD64 PC, but 
later on I did a fresh install of Windows 10 64-bit; the reason for the 
architecture mismatch was that PC vendor sold AMD64 PCs with Windows 7 
Starter Edition (which was 32-bit only IIRC).
Back to lighttpd: the previous version (1.4.41) does run OK with the 
same config files.
I suspected the newer lighttpd might have been somehow incompatible with 
v 1.4.41 config files, but I have another machine with Windows 7 64-bit 
and v 1.4.45 does run OK with similar config files.
The error is non verbose: when I try to load any web page (static or 
PHP) the browser just remains *loading* for a long time and later ends 
with a timeout error page, whereas the previous lighttpd binary just 
loads the page fast. There are no logs written in access.log error.log 
or cygrunsrv.log files.
I'm not sure, but I'd guess it's a compatibility issue with Windows 10.
I have mod_access, mod_redirect, mod_rewrite, mod_magnet, mod_proxy, 
mod_fastcgi (for PHP integration) enabled.
I tried accessing it at every ip (127.0.0.1, lan ip and internet ip) 
where the previous version succeeds, to no avail.
The lighttpd (1.4.45) service also takes too long to stop and sometimes 
it just fails to do so.
I use latest PHP packages for both v 1.4.41 and v 1.4.45 tests.
I run Windows 10 April 2018 Update or Windows 10 version 1803.
Thanks in advance,


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: latest lighttpd (1.4.45) not working on Windows 10 Home Edition
  2018-11-29 14:31 latest lighttpd (1.4.45) not working on Windows 10 Home Edition Alejandro Benitez
@ 2018-12-07 14:14 ` Alejandro Benitez
  2018-12-07 15:06   ` Ken Brown
  0 siblings, 1 reply; 4+ messages in thread
From: Alejandro Benitez @ 2018-12-07 14:14 UTC (permalink / raw)
  To: cygwin

Hi,

I'd like to add more information to the report.

With the help of the IRC support channel I've managed to successfully 
run a build of a later version of lighttpd (v 1.4.52) which is the 
latest tarball available at

https://www.lighttpd.net/download/

with the following build configuration

`./configure --without-bzip2 --with-openssl --with-lua`

The build is quite identical to the Cygwin build; I did not have to 
tweak my configuration files and everything worked as expected, whereas 
the current Cygwin package (v 1.4.45) shows the behavior I previously 
reported.

Best regards,


El 29/11/2018 a las 11:31 a.m., Alejandro Benitez escribió:
> Hi,
> Id like to share that the latest Cygwin lighttpd package does not work
> for me on Windows 10 Home Edition. Neither 32-bit nor 64-bit package. I
> had the chance to test it on both architectures because when I first ran
> into this problem I was running Windows 10 32-bit on this AMD64 PC, but
> later on I did a fresh install of Windows 10 64-bit; the reason for the
> architecture mismatch was that PC vendor sold AMD64 PCs with Windows 7
> Starter Edition (which was 32-bit only IIRC).
> Back to lighttpd: the previous version (1.4.41) does run OK with the
> same config files.
> I suspected the newer lighttpd might have been somehow incompatible with
> v 1.4.41 config files, but I have another machine with Windows 7 64-bit
> and v 1.4.45 does run OK with similar config files.
> The error is non verbose: when I try to load any web page (static or
> PHP) the browser just remains *loading* for a long time and later ends
> with a timeout error page, whereas the previous lighttpd binary just
> loads the page fast. There are no logs written in access.log error.log
> or cygrunsrv.log files.
> I'm not sure, but I'd guess it's a compatibility issue with Windows 10.
> I have mod_access, mod_redirect, mod_rewrite, mod_magnet, mod_proxy,
> mod_fastcgi (for PHP integration) enabled.
> I tried accessing it at every ip (127.0.0.1, lan ip and internet ip)
> where the previous version succeeds, to no avail.
> The lighttpd (1.4.45) service also takes too long to stop and sometimes
> it just fails to do so.
> I use latest PHP packages for both v 1.4.41 and v 1.4.45 tests.
> I run Windows 10 April 2018 Update or Windows 10 version 1803.
> Thanks in advance,
>
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: latest lighttpd (1.4.45) not working on Windows 10 Home Edition
  2018-12-07 14:14 ` Alejandro Benitez
@ 2018-12-07 15:06   ` Ken Brown
  2018-12-08  0:29     ` Alejandro Benitez
  0 siblings, 1 reply; 4+ messages in thread
From: Ken Brown @ 2018-12-07 15:06 UTC (permalink / raw)
  To: cygwin

[Please don't top-post on this list.]

On 12/7/2018 9:13 AM, Alejandro Benitez wrote:
> Hi,
> 
> I'd like to add more information to the report.
> 
> With the help of the IRC support channel I've managed to successfully
> run a build of a later version of lighttpd (v 1.4.52) which is the
> latest tarball available at
> 
> https://www.lighttpd.net/download/
> 
> with the following build configuration
> 
> `./configure --without-bzip2 --with-openssl --with-lua`
> 
> The build is quite identical to the Cygwin build; I did not have to
> tweak my configuration files and everything worked as expected, whereas
> the current Cygwin package (v 1.4.45) shows the behavior I previously
> reported.

Out of curiosity, I downloaded the source for the Cygwin build, and your build 
is not identical with it.  If your goal is to provide useful information for the 
lighttpd maintainer, you should use the same configure options that he used.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: latest lighttpd (1.4.45) not working on Windows 10 Home Edition
  2018-12-07 15:06   ` Ken Brown
@ 2018-12-08  0:29     ` Alejandro Benitez
  0 siblings, 0 replies; 4+ messages in thread
From: Alejandro Benitez @ 2018-12-08  0:29 UTC (permalink / raw)
  To: cygwin

> Please don't top-post on this list.
Yikes. I intended not to top-post, but it seems that replying from a 
forwarded copy (I forward Outlook.com email to another email provider) 
is no good. I've reconfigured my email client hoping I fixed it.
> Your build is not identical with it.
I remember choosing that word; I should have gone with "similar".

> If your goal is to provide useful information for the lighttpd 
> maintainer, you should use the same configure options that he used.
I wanted to somehow ameliorate my first post with the bits I could 
recently gather because I considered them sort of good news, but I'll 
try to reproduce lighttpd package ASAP and report back.

Alejandro


El 07/12/2018 a las 12:06, Ken Brown escribió:
> [Please don't top-post on this list.]
>
> On 12/7/2018 9:13 AM, Alejandro Benitez wrote:
>> Hi,
>>
>> I'd like to add more information to the report.
>>
>> With the help of the IRC support channel I've managed to successfully
>> run a build of a later version of lighttpd (v 1.4.52) which is the
>> latest tarball available at
>>
>> https://www.lighttpd.net/download/
>>
>> with the following build configuration
>>
>> `./configure --without-bzip2 --with-openssl --with-lua`
>>
>> The build is quite identical to the Cygwin build; I did not have to
>> tweak my configuration files and everything worked as expected, whereas
>> the current Cygwin package (v 1.4.45) shows the behavior I previously
>> reported.
> Out of curiosity, I downloaded the source for the Cygwin build, and your build
> is not identical with it.  If your goal is to provide useful information for the
> lighttpd maintainer, you should use the same configure options that he used.
>
> Ken
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-12-08  0:29 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-29 14:31 latest lighttpd (1.4.45) not working on Windows 10 Home Edition Alejandro Benitez
2018-12-07 14:14 ` Alejandro Benitez
2018-12-07 15:06   ` Ken Brown
2018-12-08  0:29     ` Alejandro Benitez

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).