Re: [WebDNA] lighttpd problem with returnraw http header
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 113981
interpreted = N
texte = 1581 --f403045dbfde0dc0d805655ec8cb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'm with you Ken! LOL can't blame him as I just googled lighthttp and they selling it as "lighttpd is an open-source web server optimized for speed-critical environments while remaining standards-compliant, secure and flexible. Wikipedia
"" Stable release : 1.4.48 (November 11, 2017; 3 months ago).... ---------------------------------------------------------------------------= --------------------------------------- People read this and think they have a "speed-critical" "compliant" server that is easy to setup! Easy never taught anyone anything! LOL On Fri, Feb 16, 2018 at 1:43 PM, Kenneth Grome wrote: > > Yeah I know, apache, older versions, etc=E2=80=A6 There are solutions > > but that does not solve the problem or answer my question. > > Noah, > > Any time a person chooses to be a 'pioneer' by doing something > different from most everyone else -- such as using lighttpd when > practically everyone else uses apache -- he will also have to find > his own answers and solve his own problems when things don't work > the way he wants or expects them to. > > You took a first step in this process by asking about your > problems on a WebDNA talk list. So far you've received a simple > suggestion that would easily resolve all your error page issues > (revert back to the previous lighttpd version) but you're > apparently unwilling to consider this option. Nor have you > suggested that you'd be willing to switch to apache where no one > complains about your issues. > > Apparently this leaves you with no other alternative than to use > WebDNA differently than in the previous version of lighttpd ... > and hope that it can produce most of the results you were getting > before the upgrade ... > > > > It has all worked fine till lighttpd 1.4.45, now with 1.4.46 > > something changed: Now it works kinda for 404,301,302. It does > > not with 200 (I get 2 headers in the http response, only the > > first is used, the second is shown as plain text, but then the > > content-length is not correct=E2=80=A6 - idk). Also 401: The server > > answers with a 401 but does not deliver my html-error-page but > > delivers the standard html =E2=80=9C401 - Unauthorized=E2=80=9D... > > From your description here it would seem that lighttpd 1.4.46 > ignores WebDNA when someone is "Unauthorized" to access a page. > Instead lighttpd responds directly to the browser with its own 401 > errors. In this situation the use of WebDNA's ErrorMessages.db > will not fix the problem because WebDNA is not invoked. So unless > you can figure out how to configure lighttpd to send these > requests to WebDNA, or modify lighttpd's default Unauthorized > error page to make it respond the way you want, you're stuck with > these 401 errors as they currently exist. > > The problem you described with two headers in 200 responses may be > caused by lighttpd creating one of those headers and WebDNA > creating the other one, or maybe WebDNA is creating both. Either > way it seems that WebDNA is being invoked on these page requests, > which also suggests that you may be able to use WebDNA's > post-processing feature to find and remove the unwanted header. > > I don't know what "kinda works" means for your 404, 301 and 302 > pages, but I think you've been given pretty much all the info > you'll need in order to try to make WebDNA resolve most of your > problems without reverting to an earlier version of lighttpd or > replacing it with apache. > > Good luck! > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us > archives: http://www.webdna.us/page.dna?numero=3D55 > Bug Reporting: support@webdna.us > --f403045dbfde0dc0d805655ec8cb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'm with you Ken! LOL can't blame him as I just go= ogled lighthttp and they selling it as "
lighttpd is an ope= n-source web server optimized for speed-critical environments while remaini= ng standards-compliant, secure and flexible.=C2=A0Wikipedia
-----------------------------------------------------------------= -------------------------------------------------
People read t= his and think they have a "speed-critical" "compliant" server that is easy to setup! Ea= sy never taught anyone anything! LOL