[email protected]([email protected]) on 2020.02.12 00:07:19 -0500: > Hey Benoit, > > Let me start by saying I know you're doing this as volunteer work and I > hardly need or expect them to be fixed any time soon; thank you again for > taking a look. Open source maintenance is a bigger burden than we usually > acknowledge. > > On February 11, 2020 6:49:12 PM EST, Sebastian Benoit <[email protected]> > wrote: > >Hi, > > > >Nick([email protected]) on 2020.02.11 12:15:48 +0000: > >> Ah I step in a giant puddle of egg for my first post here. My lines > >were all too long and my sample code had typos. Let's try this again: > > > >To me it looks like the obvious solution is not to use a protocol > >intended > >for tls connections with a protocol for http connections. > > > >Your reports are a mix of misunderstanding the configuration, some > >valid > >remarks about possible documentation improvements and some real bugs. > > Of course I misunderstood. That's kind of my whole point. It would have been > immediately cleared up if relayd noticed I was trying to mix HTTPS and HTTP > backends and told me that that wasn't allowed, or noticed that I had used a > protocol template in two relays, one of which it didn't really make sense in, > and stopped me. > > But it didn't stop me; in this particular thread, it instead guesses the best > it can and ends up mixing the `forward to <app>` from the second relay with > the `listen on 0.0.0.0 port 80` from the first. In the other thread , it > routes TLS traffic to a plaintext HTTP backend without warning. > > I'm asking for these errors to be explicit instead of leaving subtle > misconfigurations. > > >Because its getting confusing here what you actually try to do, I'm > >going to > >disregard this and the other reports i have not replied to. At least > >until > >the ones i replied to are resolved. > > > > I'm trying to hook together several vhosts and webapps onto a single port, > so I don't have ugly :port parts in my URLs. The webapps that speak > FastCGI I can put behind httpd location or server blocks, but the others I > can't, so I turned to relayd. > > But regardless, I gave isolated test cases for all the issues I ran into > trying to teach myself, it shouldn't matter what my original goal was, > unless you think I'm stretching relayd beyond it's intended use.
Yes, thanks for the detailed reports. It's just too much information to work on all of them at once. I will go through all of them, but not right away. Also i don't know if you got any useful feedback on reddit. IF you have a configuration question, [email protected] is usually a good place to ask, Best regards, Benno
