user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Vlastimil Babka <>
Cc: Konstantin Ryabitsev <>
Subject: "Deep-linking prevented" when clicking xz attachment at
Date: Fri, 11 Mar 2022 17:13:00 +0100	[thread overview]
Message-ID: <> (raw)


When opening:

And clicking at [-- Attachment #4: dmesg.xz --]
Which links to

I get with a high probability a "Deep-linking prevented" response instead of
the attachment. In Firefox and Chrome. Sometimes it does succeed and
provides the attachment. When opening the attachment URL directly so that
there's no Referer, it succeeds reliably. Other people confirmed this too.
Reporting here per Konstantin's advise.


             reply	other threads:[~2022-03-11 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 16:13 Vlastimil Babka [this message]
2022-03-15 20:45 ` [PATCH] www: loosen deep-linking prevention 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this inbox:

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).