From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [PATCH 4/8] www: do not double-clean Message-IDs from internal DBs
Date: Sat, 13 Aug 2016 23:53:16 +0000 [thread overview]
Message-ID: <20160813235320.10831-4-e@80x24.org> (raw)
In-Reply-To: <20160813235320.10831-1-e@80x24.org>
Ensure we always strip one level of '<>' from Message-IDs,
since our internal SQLite, Xapian, and SHA-1 storage all
assume that.
Realistically, we may screw up if somebody has '<<' or '>>',
but those are screwed up mail clients.
---
lib/PublicInbox/Feed.pm | 3 +--
lib/PublicInbox/Hval.pm | 1 -
lib/PublicInbox/View.pm | 2 +-
3 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/lib/PublicInbox/Feed.pm b/lib/PublicInbox/Feed.pm
index 232a91c..25fec10 100644
--- a/lib/PublicInbox/Feed.pm
+++ b/lib/PublicInbox/Feed.pm
@@ -266,8 +266,7 @@ sub feed_entry {
my $midurl = $feed_opts->{midurl};
my $header_obj = $mime->header_obj;
- my $mid = $header_obj->header_raw('Message-ID');
- defined $mid or return;
+ my $mid = mid_clean($header_obj->header_raw('Message-ID'));
$mid = PublicInbox::Hval->new_msgid($mid);
my $href = $midurl . $mid->{href}. '/';
diff --git a/lib/PublicInbox/Hval.pm b/lib/PublicInbox/Hval.pm
index ab05238..b354aa4 100644
--- a/lib/PublicInbox/Hval.pm
+++ b/lib/PublicInbox/Hval.pm
@@ -32,7 +32,6 @@ sub new {
sub new_msgid {
my ($class, $msgid) = @_;
- $msgid = mid_clean($msgid);
$class->new($msgid, mid_escape($msgid));
}
diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm
index 47ffc62..5b352d1 100644
--- a/lib/PublicInbox/View.pm
+++ b/lib/PublicInbox/View.pm
@@ -491,7 +491,7 @@ sub _msg_html_prepare {
$ctx->{-upfx} = '../';
}
my @title;
- my $mid = $hdr->header_raw('Message-ID');
+ my $mid = mid_clean($hdr->header_raw('Message-ID'));
$mid = PublicInbox::Hval->new_msgid($mid);
foreach my $h (qw(From To Cc Subject Date)) {
my $v = $hdr->header($h);
--
EW
next prev parent reply other threads:[~2016-08-13 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 23:53 [PATCH 1/8] import_slrnspool: reimplement using fast-import Eric Wong
2016-08-13 23:53 ` [PATCH 2/8] searchidx: do not release Xapian lock while (only) Msgmap is indexing Eric Wong
2016-08-13 23:53 ` [PATCH 3/8] www: do not unecessarily escape some chars in paths Eric Wong
2016-08-13 23:53 ` Eric Wong [this message]
2016-08-13 23:53 ` [PATCH 5/8] mid: no wide characters for sha1_hex Eric Wong
2016-08-13 23:53 ` [PATCH 6/8] view: allow for missing In-Reply-To mapping Eric Wong
2016-08-13 23:53 ` [PATCH 7/8] view: remove redundant pre closing tag Eric Wong
2016-08-13 23:53 ` [PATCH 8/8] squash Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160813235320.10831-4-e@80x24.org \
--to=e@80x24.org \
--cc=spew@80x24.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).