Hello, Am 14.09.2007 um 03:54 schrieb Shaun Burriss:
> Unfortunately we are still unable to identify how the users have > come across the error, Oh, I know that and I have no solution to it either. I pondered about it for some time. My error is com- pletely different and it is probably caused by some code changes a former programmer here at our site did to change the sorting criteria in result display while browsing collections. This is why I did not ask about it here on the list. But when it comes to tracking down the problem, we probably face the same hurdles. First, The resulting error page produces a nice standard HTTP 200 reply in the server logs which makes it hard to identify. It looks better for the user this way, but it makes it harder to debug. I dont like the idea to remove the error page functionality from our DSpace instance only to get better log entries, leaving users with an ugly Tomcat error page and no way back. Second, the requests dont have a referrer. They come from search engine crawlers and due to their distri- buted nature they decide not to unveil how they came across this URL. Maybe, they even forge the URL fol- lowing some undisclosed logic and we dont need to worry about it because there is no such link on our site, but I am not sure. And users usually keep quiet if the have the same experience instead of shouting and helping me to fix it. Google webmaster tools did not help me to analyze it either. They just cant because they cant identify the result as an error page. You would need to use your own spider which is able to visualize the site struc- ture to find where the links com from. Some years ago, this software (I guess Mercury Interactive offered such thing) was really expensive and it ran under Windows only which is not an option for me (you dont want to run such thing in a emulation). So I did not follow this road yet. > We are getting many error messages now where the parameters are > either not present, or incorrect. Here's another example: > > An internal server error occurred on http://images.swinburne.edu.au: > > Date: 9/13/07 7:34 PM > Session ID: 21281CDDD8AF073FB042ADC14A8FFEB0 > > -- URL Was: http://images.swinburne.edu.au/mydspace/ > subscriptions.jsp?updated=0&collections=14 > -- Method: GET > -- Parameters were: > -- collections: "14" > -- updated: "0" Oh forget about this specific request. Sorry I did not mention it. This is probably from me investigating the problem. I searched for some collection which was not empty and really typed this into the browser. The only thing I cant interpret is your time stamp. But it is probably from your local zone and thus does not fit the time stamp from my reply. You can compare it because you have the deviance from GMT in the header of my message. The result of this test was partly expected. I got the same error. I expected an error but actually hoped that it would tell me that I am not logged in (carry no con- text) or that I have not subscribed to this collection (because the guest user has no subscriptions). Unhappily DSpace is not that specific in what it reports. I am not even sure whether parameters handed over in the URL or by POST Method during normal operations. If you find a good way to analyze such errors, let us know. I hope the developers take the time to read my long post. I could not judge this behaviour as being a bug and I have no suggestion how they should change it, so I did not file a report so far. But it is worth thinking about because it discourages me to do more changes that I have in mind to enhance the user ex- perience. I took a look into manakin in the hope that developing own themes is easier there but I have still a long way to go until I feel comfrotable with XSLT. And you have invested that much in you great looking JSPUI that this probably not the way to go in the short run. Bye, Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
