1.88 KB, text/plain
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.0) Gecko/20020529 BuildID: 2002052918 According to them (in an eamil) they don't support the mac platform at all !!!BUT!!! 1) if I try IE 5.1 for mac, there's no problem 2) if I spoof the UserAgent with uabar (http://uabar.mozdev.org/) to say that Mozilla is IE 5.5 Win, there's no problem Reproducible: Always Steps to Reproduce: 1. go to to URL given Actual Results: access is refused with this error message: De kan desværre ikke se dette websted med Deres nuværende browser. Webstedet kan ses med Internet Explorer version 5 eller nyere Netscape Navigator version 6 eller nyere translation (for the multilingually inhibited :-D ): Unfortunately, you can't see this website with your present browser. The website can be seen with Internet Explorer version 5 or newera Netscape Navigator version 6 or newer Expected Results: ought to work perfectly in lieu of their stated requirements I've written twice to their info-email. The first response contained more of the same nonsense as the error message. I'm at present awaiting a response to my second email. I'll report their answer here if/when it arrives
Severity: minor → major
Summary: [www.daab-as.com] refuses access for mozilla on mac → daab-as.com - refuses access for mozilla on mac
I gave it "minor" because by using uabar you can easily get the site to work
Confirmed using FizzillaCFM/2002052918 (rv1.0.0). Accessed is blocked.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Bjarne, most people don't use the UABar and it is not supplied with Mozilla by default.
looks ok with Mozilla/Linux - really only blocking the Mac-version?
As of today, they are !!!STILL!!! un-necessarily blocking access from Mac :-(( My latest attempt was Mac OS 9.1 And it's serverside blocking, so spoofing the user agent is the only option on our side if we wish access And I've received no response to my latest email :-(( This is apparently a hard case :-((
havefix: they should know that gecko mac is the same as gecko on every other platform (minus the bugs :) . setting P2/critical. now that the new aol client for macosx is out with gecko, this kind of bugs need to be fixed :))
Severity: major → critical
Priority: -- → P2
Whiteboard: [DENY] → [DENY][havefix]
Created attachment 95072 [details] letter written to daab-as (in Danish - sorry :-) ) That's exactly what I've explained to them :-)
What exactly is the criteria for marking an evangelism bug as critical? There are lots of web sites that pointlessly reject Gecko browsers. Is there something special about daab-as.com, or should we be marking critical on dozens of other bugs? Also, I was under the impression that only the actual engineers working on a bug should set a Priority level. Are there any official guidelines? The overview at http://bugzilla.mozilla.org/bug_status.html is insufficient.
[~off topic] The evangelism component is a bit special :) The guidelines for those bugs have recently changed, see http://www.mozilla.org/projects/tech-evangelism/site/procedures/bug-fields.html There used to be some cases when you should put p2/critical for such bugs, but not any more :) (and btw I did work on this bug as I was part of the netscape evangelism team at that time, and that bug was critical for us because of the release of the macosx aol client... :) but looks like nobody had time to evangelize that site a bit more...)
move tristans bugs to other
Assignee: nitot → other
Component: Europe: West → Other
QA Contact: brantgurganus2001 → other
INCOMPLETE due to lack of activity since the end of 2009. If someone is willing to investigate the issues raised in this bug to determine whether they still exist, *and* work with the site in question to fix any existing issues, please feel free to re-open and assign to yourself. Sorry for the bugspam; filter on "NO MORE PRE-2010 TE BUGS" to remove.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.