edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] interesting finding: localizeweb=en
Date: Tue, 16 Jan 2018 06:49:08 -0500	[thread overview]
Message-ID: <20180016064908.eklhad@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

Kevin writes:
> I found that I can get in to amazon even with a one line .ebrc:
> localizeweb = en
> Fails without it, logs me in with it. What is this??

Well now who would have guessed that?
I almost forgot myself, so this is from the users guide.

Some websites offer their contents in multiple languages.
For example, twitter.com has an English version, a French version, and so forth.
It is possible to select the language when requesting the page.
Edbrowse supports this via the localizeweb keyword in its configuration file.
For instance, the following entry in .ebrc indicates that you want the French
version, when it is available.

localizeweb = fr

At a more technical level, it sends

Accept-Language: en

in the outgoing http headers.
This should have shown up as a difference between our two log files, right at line 11.
But ok, why should that matter?
Why wouldn't it guess English like every other website?
Or put up a menu of choices?
That is very mysterious.

If it holds up then I need to ask you all a question. Should I

1. Add, to the users guide, a warning that this directive should be included, since some important websites won't work without it.

2. Automatically send this http directive if you don't specify it, according to your LANG parameter.
I would of course document that behavior.

Karl Dahlke

             reply	other threads:[~2018-01-16 11:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 11:49 Karl Dahlke [this message]
2018-01-16 13:02 ` Chuck Hallenbeck
2018-01-16 21:16   ` Kevin Carhart
2018-01-25 19:58     ` Adam Thompson
2018-01-25 20:05       ` Karl Dahlke
2018-01-26 17:49         ` Adam Thompson

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=20180016064908.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.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).