Date | Commit message (Collapse) |
|
We've cleaned up our code in recent days and WwwStream
provides a consistent header for our HTML pages.
|
|
Reduce the size of hashes a bit and drops some unneeded hash
lookups for uncommon paths.
|
|
We no longer generate our footer, here. We are not currently
advertising ssoma, here.
|
|
Danga::Socket::write will set the closed flag on a socket,
automatically, and we do not need to bring down an entire
server when one client breaks the connection :P
|
|
Same as nginx :>
|
|
Our nntpd and httpd are similar so configuration differences
should be minimized
|
|
We already add the extra newline when we call print.
|
|
There was a spurious test failure in t/httpd-corner.t
which I have not been able to reproduce.
|
|
Fixes: 33cef7f24d3d ("config: introduce each_inbox for iteration")
|
|
This is closer to the behavior of thread-aware MUAs.
|
|
It should be harmless if the "[this message]" text goes past
the boundary as we bold the entire line to make it stand out.
|
|
No need for ' / ' delimiters on lines dedicated for hyperlinks.
|
|
We now generate all of our HTML using WwwStream which
forces us to have consistent headers and footers in
the HTML itself.
This also makes the search-capable vs search-less installs
go to the new.html endpoint to maintain consistency
(in case an admin decides to enable Xapian).
|
|
This fixes some layering violations and consolidates
the cleanup into the inbox object itself. Keeping in
mind weakening does not work at all without our PSGI
server.
|
|
We should not fail tests when this is not available.
|
|
No need to keep an extra array around for this.
|
|
Oops...
|
|
We only need XHTML-compatibility inside Atom feeds, as
anecdotally, feed readers are stricter than normal browsers and
some do not support HTML, only XHTML. So we will continue to
accomodate them. However we favor HTML elsewhere since it
tends to be smaller than the equivalent well-formed XHTML.
|
|
Oops :x
|
|
Another step towards a consistent WWW UI...
|
|
Automatic inbox switching was a potentially deceptive pattern
and surprises readers who do not check the URL bar closely.
Furthermore, a message could be cross-posted to multiple lists,
too.
|
|
This can be use to specify a small response using -html_tip.
|
|
They're uncommon, fortunately, but we make no attempt to
handle nested comments (which would open us up to things
like CVE-2015-7686) or use the comment in place of a
missing name.
|
|
Exposing compressed Message-IDs in URLs was a mistake,
remove a remnant of it.
|
|
If using a master/worker setup, a careless user could be trying
to signal all processes using "killall". This may trigger bad
side-effects; but try to limit the side-effects as much as
possible.
|
|
Oops :x
|
|
Document and simplify things a bit. The major functional change
is we no longer waste space caching objects from dumb HTTP
clones.
|
|
We don't need to care about client IPs anywhere.
|
|
There is no point for diverting readers' attention with
an unnecessary link, here.
|
|
This will allow cache proxies such as Varnish to avoid
caching data sent by us.
|
|
git.git documentation uses "clonable" so that's probably
a better term than "clone-able". Also, shorten the section
for retrieving our code and remove an obvious typo.
|
|
This avoids breaking clients on graceful shutdown since
NNTP responses should usually be quick.
|
|
This ought to make things easier when we add TLS support.
|
|
This fills in the internal lookup hashes and simplifies
callers.
|
|
GoogleGroups URLs often contain '!' in them
|
|
Lighter and ever-so-slightly faster!
Most importantly, this won't do non-obvious stuff behind our
backs like trying to parse a POST request body for a query
string param.
|
|
Plack::Request will check the request body by merely
calling "param", totally unnecessary and sneaky.
|
|
More work on on the Plack::Request/CGI.pm removal front,
No need to access the PSGI env through an extra hash lookup.
|
|
This is less code and hopefully easier-to-understand.
|
|
This is lighter and we can work further towards eliminating
our Plack::Request dependency entirely.
|
|
I bet there's a billion other improvements to be made elsewhere.
|
|
|
|
Well, I'm fumbling along with this config. Might as well
fumble along with it publically :)
|
|
|
|
Oops, fortunately this branch is only exposed to non-Xapian
users, right now.
|
|
It seems common for address entries to end up as:
"foo@example" <foo@example>
Avoid needlessly displaying the domain name in that case.
|
|
It's browseable, too!
|
|
Probably better than bloating our own API with configurable
warning streams and such...
|
|
Note to self: remember to run tests
Fixes: 52052329aced ("git: allow cloning from the URL root, too")
|
|
This means we can still show non-git users a somewhat browseable
URL with a link to the README.html file while allowing git users
to type less when cloning.
All of the following are supported:
git clone https://public-inbox.org/ public-inbox
git clone https://public-inbox.org/public-inbox
git clone https://public-inbox.org/public-inbox.git
torsocks git clone http://ou63pmih66umazou.onion/public-inbox
|