Re: syntax error in httpd.conf file

2024-04-20 Thread Peter N. M. Hansteen
On Sat, Apr 20, 2024 at 08:47:23AM -0600, deich...@placebonol.com wrote: > continuing with man page recommendations, when you read entirely to the end > of a man page you will see reference to related man pages. At the end of > httpd man there are several references, including httpd.conf this

Re: syntax error in httpd.conf file

2024-04-20 Thread deich...@placebonol.com
continuing with man page recommendations, when you read entirely to the end of a man page you will see reference to related man pages. At the end of httpd man there are several references, including httpd.conf On April 19, 2024 8:58:34 PM MDT, Alexis wrote: >"Luca Leone" writes: > >> I could

Re: syntax error in httpd.conf file

2024-04-20 Thread Alexis
"Peter N. M. Hansteen" writes: Here's the story of my asking it to write a PF.conf - https://nxdomain.no/~peter/chatgpt_writes_pf.conf.html or with nicer formatting and trackers https://bsdly.blogspot.com/2023/06/i-asked-chatgpt-to-write-pfconf-to-spec.html so in this context, near totally

Re: syntax error in httpd.conf file

2024-04-20 Thread Peter N. M. Hansteen
On Sat, Apr 20, 2024 at 12:58:34PM +1000, Alexis wrote: > > and a bit surprinsigly - at least to me - chatgpt didn't get the syntax > > right either, no matter how detailed my prompt was. > > Not at all surprising to me, given that ChatGPT and other LLM-based 'AI' > systems - essentially Markov

Re: syntax error in httpd.conf file

2024-04-20 Thread Alexis
"Luca Leone" writes: thanks Alexis for pointing me to the right resources! Actually I did a search in the man pages, but I searched for "httpd" which gave me the page for httpd, and rightly so, page that was not useful for my problem. I *didn't *search for "httpd.conf", which would have

Re: syntax error in httpd.conf file

2024-04-20 Thread Luca Leone
thanks Alexis for pointing me to the right resources! Actually I did a search in the man pages, but I searched for "httpd" which gave me the page for httpd, and rightly so, page that was not useful for my problem. I *didn't *search for "httpd.conf", which would have been much more useful. I

Re: syntax error in httpd.conf file

2024-04-19 Thread Alexis
"Luca Leone" writes: I could not find much online on how to write these two guys: httpd.conf and relayd.conf On OpenBSD, the first places to check for documentation are: * the man(ual) pages, which can be accessed from the command line, e.g. $ man httpd.conf $ man relayd.conf but

Re: syntax error in httpd.conf file

2024-04-19 Thread Luca Leone
WOW! it works, super happy right now, after many (interesting) hours trying to make it work with a lot of not-so-useful help from chatgpt ;) Maybe then I will not leave openBSD... I simply have to improve my skills :) Thanks Kirill!!! Any good resourse you'd like to point me to, to improve on

Re: syntax error in httpd.conf file

2024-04-19 Thread Kirill A . Korinsky
On Fri, 19 Apr 2024 13:30:47 +0200, Luca Leone wrote: > > I'll keep working on it, but after a couple of days spent on this stuff I'm > starting to think that maybe to serve my node app there should be an easier > way than openbsd ;) > I guess you mean someting like that? table { 127.0.0.1

Re: syntax error in httpd.conf file

2024-04-19 Thread Luca Leone
wonderful, thanks Omar! somehow I missed it! my bad. I wrote a basic relayd.conf, which of course doesn't work. http protocol "http" { match request header set "X-Forwarded-For" value "$REMOTE_ADDR" } relay "web" { listen on 0.0.0.0 port 443 tls protocol "http" forward to 127.0.0.1

Re: syntax error in httpd.conf file

2024-04-18 Thread Omar Polo
Hello, On 2024/04/18 22:29:55 +0200, "Luca Leone" wrote: > Hi guys! > > [...] > > If is change `pass to "http://localhost:3000/"` with a simple `root > "/var/www/htdocs"` directive, > the syntax check is OK. > > The reason for the `pass to "http://localhost:3000/"` directive is that I am >

syntax error in httpd.conf file

2024-04-18 Thread Luca Leone
Hi guys! this is the content of my httpd.conf file: server "birbi.biz" { listen on * port 80 location "/.well-known/acme-challenge/*" { root "/acme" request strip 2 } location * { block return 301 "https://$HTTP_HOST$REQUEST_URI; } } server