public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@lycos.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: user agent switcher - automatic
Date: Mon, 13 Feb 2006 23:19:10 +0000	[thread overview]
Message-ID: <dsr44d$vnb$1@sea.gmane.org> (raw)
In-Reply-To: 200602132129.44114.harmgeerts@home.nl

Harm Geerts wrote:

> On Monday 13 February 2006 20:56, Joseph wrote:
>> I remember there was some kind of user agent for Mozilla (before
>> firefox) that worked per url basis.
>>
>> Anyhow, the current user agent doesn't help me.  I can seem to fool
>> Canada Post web-loging screen with Firefox - user agent (it display
>> log-in screen) but when I try to create an account it'll not the spoof.
>> Can anybody try it:
>> http://www.canadapost.ca/business/obc/default-e.asp?sblid=obc
>> There is a link on the right: "New user... click here"
> 
> As soon as the login page finishes loading I get redirected to a 404 page,
> I don't even get the chance to do anything...
> 
> You really should send an email to them about it and let them know they're
> missing (give or take) 10% of potential customers by filtering
> firefox/gecko browsers.
> 
> With the browser requirements they have I'll never be able to register...
> Their world stops with IE and netscape, IE obviously doesn't run native on
> linux, and netscape is masked for amd64.
> 
> webdevelopment, it's a dirty business :-)

Their server sends a test cookie which discriminates against decent
browsers!  Firefox won't play.  Opera falls apart irrespective of how I set
it to identify itself.  The same happens with Konqueror in the default user
agent setting, but it logs in happily in the IE6 setting.  Some bright
spark has written 311 lines of code in a script which actively
discriminates against most browsers & OS's out there.

Some web-developers or businesses are concerned that they provide an
identical web presence to all visitors for marketing/corporate identity
purposes.  A deformed/malfunctioning website is understandably not
acceptable for them.  Lazy wysiwyg web designers will not spend time to
trim their code for most browsers to be able to show their content as
intended.  On the other hand one can end up chasing their tail if every
browser invented has to show the same content.  There's bound to be some
differences.

I understand that Google now discriminates against websites which . . .
discriminate against particular browsers.  IE and their wysiwyg HTML
editing products have cause a lot of bad code out there and it will take
some time to people to catch up and clean their code.  Until then COMPLAIN!
-- 
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-13 23:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 18:03 [gentoo-user] user agent switcher - automatic Joseph
2006-02-13 19:42 ` [gentoo-user] " Harm Geerts
2006-02-13 19:56   ` Joseph
2006-02-13 20:29     ` Harm Geerts
2006-02-13 23:19       ` Mick [this message]
2006-02-14  0:28         ` [gentoo-user] Open Office 2.01 US Intl KB missing single & double quote characters Dave Jones
2006-02-14 17:32         ` [gentoo-user] Re: user agent switcher - automatic Neil Bothwick

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='dsr44d$vnb$1@sea.gmane.org' \
    --to=michaelkintzios@lycos.co.uk \
    --cc=gentoo-user@lists.gentoo.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