Blank Window for DocuShare Login



15 years ago
13 years ago


(Reporter: Charles Tryon, Unassigned)


Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

I'm not sure if this is a problem in Mozilla or in the Xerox DocuShare product,
but it is exactly the same symptoms as seen (and fixed) in an earlier version of
Mozilla.  It appears to have come back again.  See bug #150680

Reproducible: Always

Steps to Reproduce:
1. go to
2. Select Login from the Login | Accounts | Contents ... bar

Actual Results:  
Window is completely blank.  Page source is <html><body></body></html>

Expected Results:  
Fully populate login page asking for username, password, etc.

I have done most of my probing using a Linux (RH9/XD2) box, but I have also
convirmed that this same behavior exists under the Windows 1.4 version of
Mozilla.  It is interesting to note that I get very similar results (error
parsing XML, empty page) when running Opera (7.21 Final) under Linux.

See Also: bug #150680

Comment 1

15 years ago
*** Bug 223388 has been marked as a duplicate of this bug. ***
The site is doing some weird server-side stuff.... s_client is not allowed to
connect at all, while with Mozilla the following headers are sent back by the

16386[81294a8]: http response [
16386[81294a8]:   HTTP/1.1 400 'None' object has no attribute 'value'
16386[81294a8]:   Server: Netscape-Enterprise/6.0
16386[81294a8]:   Date: Thu, 23 Oct 2003 16:48:43 GMT
16386[81294a8]:   Content-Length: 0
16386[81294a8]:   Content-Type: text/xml
16386[81294a8]:   Docushare-version: 2.2
16386[81294a8]:   Docushare-user: Guest (User-1)
16386[81294a8]:   Docushare-error: DSErrorException 'None' object has no
attribute 'value'
16386[81294a8]: ]

oops.  Looks like something in their server code threw an exception and failed
to deal...  And of course the error page is empty.
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.