From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@googlegroups.com
Subject: Re: Linuxemu and Slackware 11.0, preliminary report
Date: Mon, 2 Apr 2012 22:58:29 +0100 [thread overview]
Message-ID: <20120402225829.2c702eab@inari.ethans.dre.am> (raw)
In-Reply-To: <22f9bb5f1e6440b7bf02a6e067a81dd1@rei2.9hal>
On Mon, 2 Apr 2012 22:51:40 +0200
cinap_lenrek@gmx.de wrote:
> you can try with something like:
>
> hget -r 'Referer: http://example.com/' http://example.com/foo.jpg
>
> to see if the problem is the missing referer header.
>
> implementing referers woul'v been the task of mothra, but i'm not
> sure if referers are a good idea even given how mutch it is abused
> for spam and user tracking these days.
>
> --
> cinap
Ah, that's it exactly. I wonder if webfs or mothra could add headers
on a site-specific basis, perhaps passing every url to a script and
incorporating what the script gives back or loading a table of <regexp>
<headers> at startup.
next prev parent reply other threads:[~2012-04-02 21:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 13:53 Ethan Grammatikidis
2012-04-02 14:02 ` sl
2012-04-02 14:16 ` Ethan Grammatikidis
2012-04-02 20:36 ` cinap_lenrek
2012-04-02 20:51 ` cinap_lenrek
2012-04-02 21:58 ` Ethan Grammatikidis [this message]
2012-04-02 22:09 ` sl
2012-04-02 23:00 ` Ethan Grammatikidis
2012-04-02 23:02 ` cinap_lenrek
2012-04-02 23:13 ` hiro
2012-04-02 23:21 ` cinap_lenrek
2012-04-02 23:23 ` Ethan Grammatikidis
2012-04-02 23:34 ` sl
2012-04-02 23:32 ` Anthony Martin
2012-04-03 6:36 ` cinap_lenrek
2012-04-02 22:58 ` cinap_lenrek
2012-04-02 23:18 ` Ethan Grammatikidis
2012-04-02 23:47 ` Kurt H Maier
2012-04-03 1:24 ` Ethan Grammatikidis
2012-04-03 6:03 ` cinap_lenrek
2012-04-03 8:17 ` Ethan Grammatikidis
2012-04-04 9:17 ` steve
2012-04-07 23:30 ` Ethan Grammatikidis
2012-04-08 0:22 ` sl
2012-04-08 2:27 sl
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=20120402225829.2c702eab@inari.ethans.dre.am \
--to=eekee57@fastmail.fm \
--cc=9front@googlegroups.com \
/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 NNTP newsgroup(s).