Re: [greenstone-users] RE: Error which will prevent the collection from being

From sw64@cs.waikato.ac.nz
DateTue, 24 Apr 2007 12:31:33 +1200 (NZST)
Subject Re: [greenstone-users] RE: Error which will prevent the collection from being
In-Reply-To (007101c785c3$496ebee0$6501a8c0-HMG2)
Hello Henry,

If you follow the standard gsdl server setup, the path sould be
http://www.hgladney.net/cgi-bin/library?c=....

You could set this up in gli->Preferences->Connection->Library Path
by entering: http://www.hgladney.net/cgi-bin/library

Regards
Shaoqun

> This continues my posting sent April 23, 2007 5:33 AM
>
> I loaded a 4000-file subset of the prior largish collection into a new
> collection. This time the Create "Build Collection" ran to completion,
> and activated the "Preview" tab. However, when I activated Preview,
> instead of showing the expected collection preview, it terminated the
> Librarian application with the following output in the terminal window
> from which "./gli.sh" had been issued.
>
> -raise
> -remote
> openURL(http://hgladney.net/home/gladney/gsdl?c=snotest2&l=en&a=p&p=about&uq=1177338374748,new-tab
>
> <http://hgladney.net/home/gladney/gsdl?c=snotest2&l=en&a=p&p=about&uq=1177338374748,new-tab>
> )
>
> So I copied the string
> "http://hgladney.net/home/gladney/gsdl?c=snotest2&l=en&a=p&p=about&uq=1177338374748
> <http://hgladney.net/home/gladney/gsdl?c=snotest2&l=en&a=p&p=about&uq=1177338374748,new-tab>
> " into the URL input field of a running Firefox browser instance. That
> returned a 404 Not Found message, which presumably is correct because the
> GSDL instance is in fact in directory /gsdl rather than in
> /home/gladney/gsdl/. And the following new file appeared in the /tmp
> directory.
>
> □ <wml>
> □ <head>
> <meta http-equiv="Cache-Control" content="max-age=0"/>
> </head>
> □<card title="Server Error in /">
> □<p>
> □<b>
> □<big>
> A potentially dangerous Request.QueryString value was detected from the
> client (=&quot;...sever.COM/&lt;Rejected-By-UrlScan...&quot;).
> </big>
> </b>
> <br/>
> Request Validation has detected a potentially dangerous client input
> value, and processing of the request has been aborted. This value may
> indicate an attempt to compromise the security of your application, such
> as a cross-site scripting attack. You can disable request validation by
> setting validateRequest=false in the Page directive or in the <pages>
> configuration section. However, it is strongly recommended that your
> application explicitly check all inputs in this case.
> <br/>
> Exception Details: System.Web.HttpRequestValidationException: A
> potentially dangerous Request.QueryString value was detected from the
> client (=&quot;...sever.COM/&lt;Rejected-By-UrlScan...&quot;).
> </p>
> </card>
> </wml>
> Trying what I thought might be the correct URL (viz.,
> http://www.hgladney.net/gsdl?c=snotest2&l=en&a=p&p=about&uq=1177338374748
> <http://hgladney.net/home/gladney/gsdl?c=snotest2&l=en&a=p&p=about&uq=1177338374748,new-tab>
> also returned a 404 message.
> What is happening & why? And more important to me, How can I recover and
> move forward?
>
> Cheerio, Henry
>
>
>>_____________________________________________
>>From: H.M. Gladney [mailto:hgladney@pacbell.net]
>>Sent:Monday, April 23, 2007 5:33 AM
>>To:'greenstone-users@list.scms.waikato.ac.nz'
>>Subject:Error which will prevent the collection from being
>>
>>With a largish collection (approximately 60,000 files, which include
>> numerous duplicates, in 36 top-level folders) I receive the message <An
>> error has occurred which will prevent the collection from being
>> previewed>. I retried. Received the same message. The build progress
>> indicator indicates 50%.
>>
>>Attempted to recover. However, in the Librarian's dialog for the Create
>> tab, "Build Collection" is enabled but the option choice between
>> "Complete Rebuild" and "Minimal Rebuild" is disabled.
>>
>>How can I proceed?
>>Is this collection in fact large from a Greenstone perspective? (I
>> believe that several collections will be this large or larger at the
>> Computer History Museum, for which I am attempting to use Greenstone.)
>>
>>Note: Greenstone Users Digest, Vol 42, Issue 17 (and also Issue 12)
>> contains a note asking about this error. Michael Dewsnip's 27 Sep 2006
>> answer includes: "This is a bug which will be fixed in Greenstone v2.71."
>> But I am running Greenstone v2.72!
>>
>>The Dewsnip answer does not include a work-around suggestion.
>>
>>Cheerio, Henry
>>
>>H.M. Gladney, Ph.D. http://home.pacbell.net/hgladney
>>
> _______________________________________________
> greenstone-users mailing list
> greenstone-users@list.scms.waikato.ac.nz
> https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users
>