all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: raman <raman@google.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22671@debbugs.gnu.org
Subject: bug#22671: 25.0.90; EWW: Redirects go to Firefox (rather than EWW)
Date: Tue, 16 Feb 2016 08:33:15 -0800	[thread overview]
Message-ID: <p91egcc62es.fsf@google.com> (raw)
In-Reply-To: <87d1rx6vdf.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 16 Feb 2016 17:07:40 +1100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

Thanks for looking at this Lars -- Agree with you -- sites out there do
all kinds of weird things with browser redirect. I had looked at the
headers with lwp-request and saw the first redirect -- and missed the
second redirect to the mp3 stream.


>
>> Sometimes, sites send a redirect  with content-type text/html  but that
>> text/html still gets handed to Firefox -- rather than EWW.
>> One possible reason is that /etc/mailcap on ubuntu/trusty has this line:
>> text/html; firefox -private-window %s; test=test -n "$DISPLAY"
>>
>> It has that for the other xml/html related mime types as well.
>
> This has nothing to do with that, it turns out, but rather with the
> eww-use-external-browser-for-content-type variable.  The URL redirects
> to something with "Content-Type: audio/mpeg", and that matches that
> variable, so it opens Firefox.
>
> I think that that's really confusing, though.  It should just render it
> as a link, and then people can do what they want with it...

-- 





  reply	other threads:[~2016-02-16 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 23:46 bug#22671: 25.0.90; EWW: Redirects go to Firefox (rather than EWW) raman
2016-02-16  6:07 ` Lars Ingebrigtsen
2016-02-16 16:33   ` raman [this message]
2017-01-24 22:39     ` Lars Ingebrigtsen

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=p91egcc62es.fsf@google.com \
    --to=raman@google.com \
    --cc=22671@debbugs.gnu.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.