search

gklyne / admiral-jiscmrd

Automatically exported from code.google.com/p/admiral-jiscmrd
MIT License
0 stars 0 forks source link

When databank silo is empty, ADMIRAL view datasets shpws incorrect "default" list #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. delete all datasets in a Databankl silo accessed by ADMIRAL (use Databank 
web interface)
2. from ADMIRAL front page, click "view datasets" link
3.

What is the expected output? What do you see instead?

Expect to see an empty list of datasets.  Actually see a list of two dummy 
datasets.

Not sure if this is a problem with Databank or ADMIRAL.

Original issue reported on code.google.com by gk-goo...@ninebynine.org on 4 Mar 2011 at 9:54

GoogleCodeExporter commented 8 years ago

Original comment by gk-goo...@ninebynine.org on 7 Mar 2011 at 10:46

GoogleCodeExporter commented 8 years ago

Original comment by bhavana....@gmail.com on 8 Mar 2011 at 10:13

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago

Original comment by bhavana....@gmail.com on 8 Mar 2011 at 6:05

GoogleCodeExporter commented 8 years ago 
When datasets are being retreieved for an empty silo, it returns "undefined".
If we try to access its length it would fail. - This bit on ADMIRAL is now 
resolved.

But the problem still exists with databank that is responsible for the 
following error

If we tried doing a

GET  https://admiral:admiral@zakynthos.zoo.ox.ac.uk/zoo/datasets

the following HTML is returned with 404 error.

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /zoo/datasets was not found on this server.</p>
<hr>
<address>Apache/2.2.12 (Ubuntu) Server at zakynthos.zoo.ox.ac.uk Port 
443</address>
</body></html>

The 404 is causing the problem. This may need to be looked into.

Original comment by bhavana....@gmail.com on 8 Mar 2011 at 6:07

GoogleCodeExporter commented 8 years ago 
I just had a quick look at the logs at databank end to check if there were any 
errors. I see no errors and the access logs tell me that /zoo/datasets was 
accessed a few times yesterday (about 5 times) and it was accessed at 10:06, 
10:12, 14:58 and 17:52 today. It returned a 200 for all of these requests. 

A quick test tells me that html page is displayed fine and an empty dictionary 
({}) is returned for text/plain or application/json. 

FYI, data is returned in either text/html, text/plain or application/json. It 
defaults to returning text/html, if the accept header does not have any of 
these vales.

Original comment by anus...@gmail.com on 8 Mar 2011 at 8:15

GoogleCodeExporter commented 8 years ago 
Many thanks for looking into this Anusha. Just found a problem with our proxy 
settings! This is the cause for 404. Thanks for your feed back.

curl http://zakynthos.zoo.ox.ac.uk/admiral-test/datasets   -u admiral:admiral 
-H "Accept: text/html" worked!

curl http://zakynthos.zoo.ox.ac.uk/zoo/datasets   -u admiral:admiral -H 
"Accept: text/html" failed!

Thanks to curl! :)

Original comment by bhavana....@gmail.com on 9 Mar 2011 at 12:41

GoogleCodeExporter commented 8 years ago

Original comment by bhavana....@gmail.com on 9 Mar 2011 at 3:35