216654 - Firebird has never fully supported Outlook Web Access - this build will not even allow me to log in

Status: VERIFIED WORKSFORME

(Firefox :: General, defect)

Description

[Mark Teel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030818 Mozilla Firebird/0.6.1+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030818 Mozilla Firebird/0.6.1+

Before this build, I could log in and read mail but when I would try to reply or
forward an email it would never open the new window to send the mail.  But now,
I enter my uname and it just blanks the screen without popping up the Outlook
login window which requires uname and passwd....

Reproducible: Always

Steps to Reproduce:
1.goto the url above
2.enter mteel
3.

Actual Results:  
blank browser screen

Expected Results:  
login popup should appear

Comment 1

[Adam Becevello]

*** Bug 216656 has been marked as a duplicate of this bug. ***

Comment 2

[Kevin Brosnan]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031027
Firebird/0.7+

WFM - entering mteel generates a login popup when enter is pressed or the link
below the logon box is clicked.

Comment 3

[José Jeria]

*** Bug 229194 has been marked as a duplicate of this bug. ***

Comment 4

[Jesse Ruderman]

The problem with the reply/forward window is bug 102481.

Comment 5

[Simon Paquet [:sipaq]]

I can't connect to the given link at all.

Without a testcase this bug report is INVALID. Please reopen this bug if you can
provide a testcase.

Comment 6

[Robert Citek]

(In reply to comment #5)
> I can't connect to the given link at all.
> 
> Without a testcase this bug report is INVALID. Please reopen this bug if you can
> provide a testcase.

Can you please explain why this bug has no test case and is being marked invalid?  Granted the 
URL to the provide Exchange server no longer accepts connections, but that does not make the 
bug invalid.  If it does, please explain.

For reference: http://bugzilla.mozilla.org/show_bug.cgi?id=229194 which I am reopenning, since 
I cannot change this one.

Regards,
- Robert

Comment 7

[Simon Paquet [:sipaq]]

Robert, since not everybody has Outlook Web Access at ome to test this on, we
need a test installation or a testcase. Without it, we simply cannot find out
what the problem is and whether it is a bug on our side or (more likely knowing
microsoft) it's a evangelism problem, because microsoft used some IE-specific
technologies on  Outlook Web Access. 

I will leave this open for a few weeks, waiting for a testcase. 

Comment 8

[Simon Paquet [:sipaq]]

*** Bug 229194 has been marked as a duplicate of this bug. ***

Comment 9

[Robert Citek]

(In reply to comment #7)
> Robert, since not everybody has Outlook Web Access at ome to test this on, we
> need a test installation or a testcase. Without it, we simply cannot find out
> what the problem is and whether it is a bug on our side or (more likely knowing
> microsoft) it's a evangelism problem, because microsoft used some IE-specific
> technologies on  Outlook Web Access. 

No doubt MS is being "uncooperative."  However, I tested connecting to Outlook Web Access with a 
few other browers on various platforms:
- works:
  Mozilla 1.6b for OS X
  Safari 1.0.1 for OS X
- not works:
  Mozilla 1.5 for Linux (Knoppix)
  Firebird 0.5 for OS X  

> I will leave this open for a few weeks, waiting for a testcase. 

I'll see if I can get an OWA setup somewhere for testing.

Thanks.
- Robert

Comment 10

[Robert Citek]

Ah-ha.  Finally, I was able to successfully connect to an Outlook Web Access (OWA) server with 
Firebird 0.7.  Instead of specifying my login as "username@domain" which is what I do using Safari, 
Mozilla 1.6b, and IE, I did not type my domain name.  I just entered my username and password.

BTW, leaving off the domain name also works for Mozilla 1.5 under Linux (Knoppix).

I still feel this is a bug, but at least now I can use Firebird at work.

Regards,
- Robert

Comment 11

[alanjstr]

Robert-

Please change the summary to something more meaningful.  If you're able to log
in, then this bug is resolved as described.  

You're also using an old build of Firebird.  I suggest getting either
latest-trunk or the 0.8 milestone which will be out soon.  0.8 is based on the
1.6 branch, so that username@domain should be there.

Comment 12

[Simon Paquet [:sipaq]]

WFM per reporter's comment. The issues noted in bug 102481 are still present though.