9front - general discussion about 9front
 help / color / mirror / Atom feed
* [9front] httpd minimal configuration
@ 2022-06-21 11:48 planless.user9
  2022-06-21 12:23 ` hiro
  2022-06-21 17:44 ` mkf9
  0 siblings, 2 replies; 13+ messages in thread
From: planless.user9 @ 2022-06-21 11:48 UTC (permalink / raw)
  To: 9front

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

Hi everyone,

I would like to set up a web server and have found two solutions that come directly with the system: rc-httpd (with werc) and httpd.

My preference would be httpd, however I can't find any documentation for it apart from the man page and unfortunately I don't know what exactly is expected in the web root. Is it possible to put static html pages directly in it, or is a cgi expected? Is there perhaps a simple example that I missed in my search on the wiki, fqa and via search engine?

I haven't quite figured out namespaces yet either, but the default configuration under /lib/namespace.httpd doesn't look to me like it would be usable without customization. (This is probably me, but I can't place "/usr/mike/www" "/n/emelieother" and "/srv/alice" or find the users and directories in my base system).

What would be the minimum namespace configuration needed to display a static page?
The namespace concept makes it safe to run both a web server and a mail server on one physical device, right?

Thank you very much in advance for advice!

[-- Attachment #2: Type: text/html, Size: 2157 bytes --]

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

* Re: [9front] httpd minimal configuration
  2022-06-21 11:48 [9front] httpd minimal configuration planless.user9
@ 2022-06-21 12:23 ` hiro
  2022-06-21 12:31   ` hiro
  2022-06-21 17:52   ` mkf9
  2022-06-21 17:44 ` mkf9
  1 sibling, 2 replies; 13+ messages in thread
From: hiro @ 2022-06-21 12:23 UTC (permalink / raw)
  To: 9front

> My preference would be httpd, however I can't find any documentation for it
> apart from the man page

that's as intended. if there is important stuff missing in the man
page, please send a patch.

> expected in the web root. Is it possible to put static html pages directly
> in it, or is a cgi expected?

httpd doesn't do cgi, only static html. feel free to read the code to
find the implementation details.

> Is there perhaps a simple example that I missed
> in my search on the wiki, fqa and via search engine?

no.

> I haven't quite figured out namespaces yet either, but the default
> configuration under /lib/namespace.httpd doesn't look to me like it would be
> usable without customization. (This is probably me, but I can't place
> "/usr/mike/www" "/n/emelieother" and "/srv/alice" or find the users and
> directories in my base system).

you are correct.

namespaces on the highest level might be a neat concept, but our
implementation sadly doesn't include an overall system security
concept.

> What would be the minimum namespace configuration needed to display a static
> page?

sorry.

> The namespace concept makes it safe to run both a web server and a mail
> server on one physical device, right?

no, practically right now, just spawn another cpu server instead.
physical separation is safer than user or namespace separation.

i'd trust the fileserver's user separation a bit more, so that's the
only place where i'd share ressources.

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

* Re: [9front] httpd minimal configuration
  2022-06-21 12:23 ` hiro
@ 2022-06-21 12:31   ` hiro
  2022-06-21 12:58     ` planless.user9
  2022-06-21 17:52   ` mkf9
  1 sibling, 1 reply; 13+ messages in thread
From: hiro @ 2022-06-21 12:31 UTC (permalink / raw)
  To: 9front

the most important documentation that will be useful for you to
understand namespaces in practice will be the man page: fork(2)

rc supports "rfork" command, so you can test it all out in your shell
interactively. grep for rfork in rc man page.

On 6/21/22, hiro <23hiro@gmail.com> wrote:
>> My preference would be httpd, however I can't find any documentation for
>> it
>> apart from the man page
>
> that's as intended. if there is important stuff missing in the man
> page, please send a patch.
>
>> expected in the web root. Is it possible to put static html pages
>> directly
>> in it, or is a cgi expected?
>
> httpd doesn't do cgi, only static html. feel free to read the code to
> find the implementation details.
>
>> Is there perhaps a simple example that I missed
>> in my search on the wiki, fqa and via search engine?
>
> no.
>
>> I haven't quite figured out namespaces yet either, but the default
>> configuration under /lib/namespace.httpd doesn't look to me like it would
>> be
>> usable without customization. (This is probably me, but I can't place
>> "/usr/mike/www" "/n/emelieother" and "/srv/alice" or find the users and
>> directories in my base system).
>
> you are correct.
>
> namespaces on the highest level might be a neat concept, but our
> implementation sadly doesn't include an overall system security
> concept.
>
>> What would be the minimum namespace configuration needed to display a
>> static
>> page?
>
> sorry.
>
>> The namespace concept makes it safe to run both a web server and a mail
>> server on one physical device, right?
>
> no, practically right now, just spawn another cpu server instead.
> physical separation is safer than user or namespace separation.
>
> i'd trust the fileserver's user separation a bit more, so that's the
> only place where i'd share ressources.
>

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

* Re: [9front] httpd minimal configuration
  2022-06-21 12:31   ` hiro
@ 2022-06-21 12:58     ` planless.user9
  2022-06-21 13:15       ` Jacob Moody
  0 siblings, 1 reply; 13+ messages in thread
From: planless.user9 @ 2022-06-21 12:58 UTC (permalink / raw)
  To: 9front

Thank you very much for your fast and helpful reply.

I will look at the source code in that case, hoping to get a simple web server set up.

Are there concrete insecurities in the implementation of namespaces?


------- Original Message -------
hiro <23hiro@gmail.com> schrieb am Dienstag, 21. Juni 2022 um 14:31:


> the most important documentation that will be useful for you to
> understand namespaces in practice will be the man page: fork(2)
>
> rc supports "rfork" command, so you can test it all out in your shell
> interactively. grep for rfork in rc man page.
>
> On 6/21/22, hiro 23hiro@gmail.com wrote:
>
> > > My preference would be httpd, however I can't find any documentation for
> > > it
> > > apart from the man page
> >
> > that's as intended. if there is important stuff missing in the man
> > page, please send a patch.
> >
> > > expected in the web root. Is it possible to put static html pages
> > > directly
> > > in it, or is a cgi expected?
> >
> > httpd doesn't do cgi, only static html. feel free to read the code to
> > find the implementation details.
> >
> > > Is there perhaps a simple example that I missed
> > > in my search on the wiki, fqa and via search engine?
> >
> > no.
> >
> > > I haven't quite figured out namespaces yet either, but the default
> > > configuration under /lib/namespace.httpd doesn't look to me like it would
> > > be
> > > usable without customization. (This is probably me, but I can't place
> > > "/usr/mike/www" "/n/emelieother" and "/srv/alice" or find the users and
> > > directories in my base system).
> >
> > you are correct.
> >
> > namespaces on the highest level might be a neat concept, but our
> > implementation sadly doesn't include an overall system security
> > concept.
> >
> > > What would be the minimum namespace configuration needed to display a
> > > static
> > > page?
> >
> > sorry.
> >
> > > The namespace concept makes it safe to run both a web server and a mail
> > > server on one physical device, right?
> >
> > no, practically right now, just spawn another cpu server instead.
> > physical separation is safer than user or namespace separation.
> >
> > i'd trust the fileserver's user separation a bit more, so that's the
> > only place where i'd share ressources.

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

* Re: [9front] httpd minimal configuration
  2022-06-21 12:58     ` planless.user9
@ 2022-06-21 13:15       ` Jacob Moody
  2022-06-21 14:06         ` planless.user9
  0 siblings, 1 reply; 13+ messages in thread
From: Jacob Moody @ 2022-06-21 13:15 UTC (permalink / raw)
  To: 9front

On 6/21/22 06:58, planless.user9 wrote:
> Thank you very much for your fast and helpful reply.
> 
> I will look at the source code in that case, hoping to get a simple web server set up.
> 
> Are there concrete insecurities in the implementation of namespaces?
> 

Some thoughts:
First off you seemed to imply that rc-httpd had to be used with werc, this is not the case.
If your goal is to just serve some static files rc-httpd on its own is more then capable. I would be
curious to hear your reasoning for preferring httpd.

Hiro claims that namespaces are not security boundaries. I think I would agree
maybe 6 months ago, but some work has been done lately to change this.
I'd argue that with chdev and auth/box we're in a much much nicer spot
in regards to making namespaces proper security boundaries, if you still disagree
with this statement I would be curious to hear what you think still needs changed.

Also you mention /lib/namespace.httpd, it _is_ expected that you customize it for your
system, modify it to place your webroot in the right spot.

However if you are using rc-httpd with aux/listen, there is a namespace file already
that takes advantage of newer security features: /rc/bin/service/!tcp80.namespace.
If you would wish to use this, cp /rc/bin/!tcp80 /rc/bin/tcp80 and cp /rc/bin/!tcp80.namespace
/rc/bin/tcp80.namespace, then customize as desired.

If you need some tips on writing/reading namespace files, check namespace(6), and the associated
(1) pages for commands mirrored in namespace files.

Thanks,
moody

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

* Re: [9front] httpd minimal configuration
  2022-06-21 13:15       ` Jacob Moody
@ 2022-06-21 14:06         ` planless.user9
  2022-06-21 18:40           ` sirjofri
  2022-06-22  6:25           ` william
  0 siblings, 2 replies; 13+ messages in thread
From: planless.user9 @ 2022-06-21 14:06 UTC (permalink / raw)
  To: 9front

Thank you very much moody!

There are no serious reasons for my preference and the rc-httpd approach is also definitely an option for me. (Especially with your instructions, which seem to be straightforward to realize.)

I'm just trying to understand the system and that's why I read "Notes on the Plan 9tm 3rd edition Kernel Source" and "The C Programming Language". An implementation in C would therefore play into my hands a bit (even more so, since I have almost no experience with scripts).

Many thanks again!

------- Original Message -------
Jacob Moody <moody@mail.posixcafe.org> schrieb am Dienstag, 21. Juni 2022 um 15:15:


> On 6/21/22 06:58, planless.user9 wrote:
>
> > Thank you very much for your fast and helpful reply.
> >
> > I will look at the source code in that case, hoping to get a simple web server set up.
> >
> > Are there concrete insecurities in the implementation of namespaces?
>
>
> Some thoughts:
> First off you seemed to imply that rc-httpd had to be used with werc, this is not the case.
> If your goal is to just serve some static files rc-httpd on its own is more then capable. I would be
> curious to hear your reasoning for preferring httpd.
>
> Hiro claims that namespaces are not security boundaries. I think I would agree
> maybe 6 months ago, but some work has been done lately to change this.
> I'd argue that with chdev and auth/box we're in a much much nicer spot
> in regards to making namespaces proper security boundaries, if you still disagree
> with this statement I would be curious to hear what you think still needs changed.
>
> Also you mention /lib/namespace.httpd, it is expected that you customize it for your
> system, modify it to place your webroot in the right spot.
>
> However if you are using rc-httpd with aux/listen, there is a namespace file already
> that takes advantage of newer security features: /rc/bin/service/!tcp80.namespace.
> If you would wish to use this, cp /rc/bin/!tcp80 /rc/bin/tcp80 and cp /rc/bin/!tcp80.namespace
> /rc/bin/tcp80.namespace, then customize as desired.
>
> If you need some tips on writing/reading namespace files, check namespace(6), and the associated
> (1) pages for commands mirrored in namespace files.
>
> Thanks,
> moody

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

* Re: [9front] httpd minimal configuration
  2022-06-21 11:48 [9front] httpd minimal configuration planless.user9
  2022-06-21 12:23 ` hiro
@ 2022-06-21 17:44 ` mkf9
  1 sibling, 0 replies; 13+ messages in thread
From: mkf9 @ 2022-06-21 17:44 UTC (permalink / raw)
  To: 9front

Hi.

planless.user9 wrote:
> My preference would be httpd, however I can't find any documentation for 
> it apart from the man page and unfortunately I don't know what exactly 
> is expected in the web root. Is it possible to put static html pages 
> directly in it, or is a cgi expected? Is there perhaps a simple example 
> that I missed in my search on the wiki, fqa and via search engine?
> 
these might be helpful for the idea of how httpd works:
https://plan9.io/wiki/plan9/httpd/index.html
http://werc.cat-v.org/docs/web-server-setup/plan-9-httpd

however, httpd is one of more complex programs that exist in 9front
and may take longer to learn.

> What would be the minimum namespace configuration needed to display a 
> static page?
> putting your files in /usr/web should be enough.
iirc.

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

* Re: [9front] httpd minimal configuration
  2022-06-21 12:23 ` hiro
  2022-06-21 12:31   ` hiro
@ 2022-06-21 17:52   ` mkf9
  1 sibling, 0 replies; 13+ messages in thread
From: mkf9 @ 2022-06-21 17:52 UTC (permalink / raw)
  To: 9front

hiro wrote:

>> expected in the web root. Is it possible to put static html pages directly
>> in it, or is a cgi expected?
> 
> httpd doesn't do cgi, only static html. feel free to read the code to
> find the implementation details.
isn't webls and man2html some are kind of cgi or i'm mistaken?

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

* Re: [9front] httpd minimal configuration
  2022-06-21 14:06         ` planless.user9
@ 2022-06-21 18:40           ` sirjofri
  2022-06-22  6:25           ` william
  1 sibling, 0 replies; 13+ messages in thread
From: sirjofri @ 2022-06-21 18:40 UTC (permalink / raw)
  To: 9front


21.06.2022 16:06:53 planless.user9 <planless.user9@proton.me>:
> There are no serious reasons for my preference and the rc-httpd 
> approach is also definitely an option for me. (Especially with your 
> instructions, which seem to be straightforward to realize.)
>
> I'm just trying to understand the system and that's why I read "Notes 
> on the Plan 9tm 3rd edition Kernel Source" and "The C Programming 
> Language". An implementation in C would therefore play into my hands a 
> bit (even more so, since I have almost no experience with scripts).

httpd is really a quite complex application, and if you want a pure C 
solution (without cgi) I suggest also looking into tcp80. There are a few 
sources for it, and I don't know if there is any canonical one.

Tcp80 is a simple binary you can copy to your service directory for the 
simplest setup. It uses /lib/namespace.httpd as the namespace file.

Since you are quite new to 9 I give you a few hints:

There is a program called aux/listen. This program listens to specific 
ports, starts associated processes and connects stdin/stdout with that 
process. Aux/listen is started by default on all cpu servers (see cpurc), 
and it listens to files in /rc/bin/service (or /cfg/$sysname/service if 
it exists).

To associate a port with a process you just have any kind of executable 
file in this directory called (protocol)(port), eg tcp443 would make 
aux/listen to port 443, and if someone calls, execute that exact file.

The program tcp80 can be placed in the service directory as is, or you 
build a wrapper rc script around it.

Most server processes like tcp80/httpd first set up their namespace 
according to the namespace.X file. Since web servers canonically are only 
interested in the /usr/web directory, the process binds this directory to 
/, which results in some nice sandboxing (eg it prevents %2f attacks).

Note that tcp80 only does GET and stuff like that, you can't POST with 
it. httpd can do a little more things, at least in its special handlers, 
like the wiki handler.

I hope this helps.

sirjofri

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

* Re: [9front] httpd minimal configuration
  2022-06-21 14:06         ` planless.user9
  2022-06-21 18:40           ` sirjofri
@ 2022-06-22  6:25           ` william
  2022-06-22  9:09             ` planless.user9
  1 sibling, 1 reply; 13+ messages in thread
From: william @ 2022-06-22  6:25 UTC (permalink / raw)
  To: 9front

Plenty of brilliant responses here in the various threads that followed. This might be
straight forward howerver.

### setup rc-httpd quick

	touch /rc/bin/rc-httpd/select-handler
	#!/bin/rc

	PATH_INFO=$location

	switch($SERVER_NAME) {
	case 172.27.0.67
		FS_ROOT=/usr/glenda/www/yoda
		exec static-or-index
	case*
		error 503
	}

	touch /usr/glenda/www/yoda/index.html
	touch /sys/doc/www
	chgrp sys /sys/doc/www
	chmod +aw www
	mv /rc/bin/service/!tcp80 /rc/bin/service/tcp80

just replace that ip address and maybe change the directories

This example uses glenda. You can easily create a user /usr/www and put everything as that 
user. But keep mind that user will need permission to that service tcp80. 

I suggest experiement with this befor emoving to werc. I assure you werc is interesting
and fun. 

Besides fqa. Here is some additional info

http://thinktankworkspaces.com/plan9/httpd-rc

Regards,
-Will



Quoth planless.user9 <planless.user9@proton.me>:
> Thank you very much moody!
> 
> There are no serious reasons for my preference and the rc-httpd approach is also definitely an option for me. (Especially with your instructions, which seem to be straightforward to realize.)
> 
> I'm just trying to understand the system and that's why I read "Notes on the Plan 9tm 3rd edition Kernel Source" and "The C Programming Language". An implementation in C would therefore play into my hands a bit (even more so, since I have almost no experience with scripts).
> 
> Many thanks again!
> 
> ------- Original Message -------
> Jacob Moody <moody@mail.posixcafe.org> schrieb am Dienstag, 21. Juni 2022 um 15:15:
> 
> 
> > On 6/21/22 06:58, planless.user9 wrote:
> >
> > > Thank you very much for your fast and helpful reply.
> > >
> > > I will look at the source code in that case, hoping to get a simple web server set up.
> > >
> > > Are there concrete insecurities in the implementation of namespaces?
> >
> >
> > Some thoughts:
> > First off you seemed to imply that rc-httpd had to be used with werc, this is not the case.
> > If your goal is to just serve some static files rc-httpd on its own is more then capable. I would be
> > curious to hear your reasoning for preferring httpd.
> >
> > Hiro claims that namespaces are not security boundaries. I think I would agree
> > maybe 6 months ago, but some work has been done lately to change this.
> > I'd argue that with chdev and auth/box we're in a much much nicer spot
> > in regards to making namespaces proper security boundaries, if you still disagree
> > with this statement I would be curious to hear what you think still needs changed.
> >
> > Also you mention /lib/namespace.httpd, it is expected that you customize it for your
> > system, modify it to place your webroot in the right spot.
> >
> > However if you are using rc-httpd with aux/listen, there is a namespace file already
> > that takes advantage of newer security features: /rc/bin/service/!tcp80.namespace.
> > If you would wish to use this, cp /rc/bin/!tcp80 /rc/bin/tcp80 and cp /rc/bin/!tcp80.namespace
> > /rc/bin/tcp80.namespace, then customize as desired.
> >
> > If you need some tips on writing/reading namespace files, check namespace(6), and the associated
> > (1) pages for commands mirrored in namespace files.
> >
> > Thanks,
> > moody
> 


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

* Re: [9front] httpd minimal configuration
  2022-06-22  6:25           ` william
@ 2022-06-22  9:09             ` planless.user9
  2022-06-22  9:29               ` umbraticus
  0 siblings, 1 reply; 13+ messages in thread
From: planless.user9 @ 2022-06-22  9:09 UTC (permalink / raw)
  To: 9front

Yes, there are really a lot of great and helpful answers written which I appreciate very much, thank you for these!

Since I am not in a hurry, I will try to understand the source code of httpd and then use this service.

If there are still difficulties, the provided tcp80 should work fine with minimal changes as described in this thread.

thanks again for the support!


------- Original Message -------
<william@thinktankworkspaces.com> schrieb am Mittwoch, 22. Juni 2022 um 08:25:


> Plenty of brilliant responses here in the various threads that followed. This might be
> straight forward howerver.
>
> ### setup rc-httpd quick
>
> touch /rc/bin/rc-httpd/select-handler
> #!/bin/rc
>
> PATH_INFO=$location
>
> switch($SERVER_NAME) {
> case 172.27.0.67
> FS_ROOT=/usr/glenda/www/yoda
> exec static-or-index
> case*
> error 503
> }
>
> touch /usr/glenda/www/yoda/index.html
> touch /sys/doc/www
> chgrp sys /sys/doc/www
> chmod +aw www
> mv /rc/bin/service/!tcp80 /rc/bin/service/tcp80
>
> just replace that ip address and maybe change the directories
>
> This example uses glenda. You can easily create a user /usr/www and put everything as that
> user. But keep mind that user will need permission to that service tcp80.
>
> I suggest experiement with this befor emoving to werc. I assure you werc is interesting
> and fun.
>
> Besides fqa. Here is some additional info
>
> http://thinktankworkspaces.com/plan9/httpd-rc
>
> Regards,
> -Will
>
>
>
> Quoth planless.user9 planless.user9@proton.me:
>
> > Thank you very much moody!
> >
> > There are no serious reasons for my preference and the rc-httpd approach is also definitely an option for me. (Especially with your instructions, which seem to be straightforward to realize.)
> >
> > I'm just trying to understand the system and that's why I read "Notes on the Plan 9tm 3rd edition Kernel Source" and "The C Programming Language". An implementation in C would therefore play into my hands a bit (even more so, since I have almost no experience with scripts).
> >
> > Many thanks again!
> >
> > ------- Original Message -------
> > Jacob Moody moody@mail.posixcafe.org schrieb am Dienstag, 21. Juni 2022 um 15:15:
> >
> > > On 6/21/22 06:58, planless.user9 wrote:
> > >
> > > > Thank you very much for your fast and helpful reply.
> > > >
> > > > I will look at the source code in that case, hoping to get a simple web server set up.
> > > >
> > > > Are there concrete insecurities in the implementation of namespaces?
> > >
> > > Some thoughts:
> > > First off you seemed to imply that rc-httpd had to be used with werc, this is not the case.
> > > If your goal is to just serve some static files rc-httpd on its own is more then capable. I would be
> > > curious to hear your reasoning for preferring httpd.
> > >
> > > Hiro claims that namespaces are not security boundaries. I think I would agree
> > > maybe 6 months ago, but some work has been done lately to change this.
> > > I'd argue that with chdev and auth/box we're in a much much nicer spot
> > > in regards to making namespaces proper security boundaries, if you still disagree
> > > with this statement I would be curious to hear what you think still needs changed.
> > >
> > > Also you mention /lib/namespace.httpd, it is expected that you customize it for your
> > > system, modify it to place your webroot in the right spot.
> > >
> > > However if you are using rc-httpd with aux/listen, there is a namespace file already
> > > that takes advantage of newer security features: /rc/bin/service/!tcp80.namespace.
> > > If you would wish to use this, cp /rc/bin/!tcp80 /rc/bin/tcp80 and cp /rc/bin/!tcp80.namespace
> > > /rc/bin/tcp80.namespace, then customize as desired.
> > >
> > > If you need some tips on writing/reading namespace files, check namespace(6), and the associated
> > > (1) pages for commands mirrored in namespace files.
> > >
> > > Thanks,
> > > moody

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

* Re: [9front] httpd minimal configuration
  2022-06-22  9:09             ` planless.user9
@ 2022-06-22  9:29               ` umbraticus
  2022-06-22 10:38                 ` hiro
  0 siblings, 1 reply; 13+ messages in thread
From: umbraticus @ 2022-06-22  9:29 UTC (permalink / raw)
  To: 9front

; cat >/bin/service/tcp80 <<.
#!/bin/rc
exec echo 'HTTP/1.1 200 OK
Content-type: text/html; charset=utf-8

<p>minimal configuration</p>'
.
; chmod +x /bin/service/tcp80

CRs probably vanished.
umbraticus

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

* Re: [9front] httpd minimal configuration
  2022-06-22  9:29               ` umbraticus
@ 2022-06-22 10:38                 ` hiro
  0 siblings, 0 replies; 13+ messages in thread
From: hiro @ 2022-06-22 10:38 UTC (permalink / raw)
  To: 9front

best answer :)

On 6/22/22, umbraticus@prosimetrum.com <umbraticus@prosimetrum.com> wrote:
> ; cat >/bin/service/tcp80 <<.
> #!/bin/rc
> exec echo 'HTTP/1.1 200 OK
> Content-type: text/html; charset=utf-8
>
> <p>minimal configuration</p>'
> .
> ; chmod +x /bin/service/tcp80
>
> CRs probably vanished.
> umbraticus
>

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

end of thread, other threads:[~2022-06-22 10:42 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-21 11:48 [9front] httpd minimal configuration planless.user9
2022-06-21 12:23 ` hiro
2022-06-21 12:31   ` hiro
2022-06-21 12:58     ` planless.user9
2022-06-21 13:15       ` Jacob Moody
2022-06-21 14:06         ` planless.user9
2022-06-21 18:40           ` sirjofri
2022-06-22  6:25           ` william
2022-06-22  9:09             ` planless.user9
2022-06-22  9:29               ` umbraticus
2022-06-22 10:38                 ` hiro
2022-06-21 17:52   ` mkf9
2022-06-21 17:44 ` mkf9

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 NNTP newsgroup(s).