Re: update failure

2022-07-22 Thread Francis Daly
On Thu, Jul 21, 2022 at 07:58:51PM -0600, Jim Taylor wrote: Hi there, > Installed nginx a couple of days ago, everything appeared to go as it > should.  This evening a was going to add some programs, and was stopped cold > at my first command.  What do i need to do to go forward? This is more a

Re: Reverse proxy forcing language in cookies

2022-07-22 Thread Francis Daly
On Tue, Jul 19, 2022 at 09:51:24PM -0400, Saint Michael wrote: Hi there, > I was asked to proxy google.com through > https://ГУГЛЭ.pl > but I need to make Google believe that clients are behind a computer > with the Russian language, not English. The question of "what do I include in a request t

Re: Problem with basic auth on nuxtjs frontend with wordpress backend

2022-07-22 Thread Francis Daly
On Wed, Jul 20, 2022 at 10:19:28AM -0400, strtwtsn wrote: Hi there, > I'm trying to add basic authentication to a nginx reverse proxy which is in > front of a nuxtjs app. > But if hangs. I've also tried it in the location section, but this hangs > too, what am I missing? What does "it hangs" me

400 Bad request (spaces in request)

2022-07-22 Thread sipopo
Hello, nginx 1.21.1 started return 400 error if exists spaces in request. But I have old clients which need supports. Maybe anyone knows workaround? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,294820,294820#msg-294820 ___ nginx mailing l

Re: 400 Bad request (spaces in request)

2022-07-22 Thread Francis Daly
On Fri, Jul 22, 2022 at 05:41:15AM -0400, sipopo wrote: Hi there, > nginx 1.21.1 started return 400 error if exists spaces in request. But I > have old clients which need supports. Maybe anyone knows workaround? spaces in urls have always been incorrect. Early nginx rejected them as broken input

Thanks for your help, Francis Daly

2022-07-22 Thread Jim Taylor
Thank you for helping me unmake a mess! I had mistyped " ' " for " ` ".  To be honest, in 60 years in this business I had never typed " `  " on purpose before, so I typed single quotes around "lsb_release -cs" Now everything seems to have run correctly, but ... When I do an apt-get update, t