Hi Monika,

the actual DSpace implementation already supports If-Modified-Since http
parameter (checked against versions 1.8+).

There is no Last-Modified neither If-Last-Modified-Since http request
parameters. Please, check the list:
http://en.wikipedia.org/wiki/List_of_HTTP_header_fields


On 29 November 2012 14:10, Monika Mevenkamp <[email protected]> wrote:

> João
>
> We are harvesting content from DSPACE instances into a LOCKSS network for
> preservation purposes. The system is setup to initially fetch content using
> HTTP get requests and  periodically check for updates  using HTTP GET with
> If-Last-Modified-Since.  We were hoping that the DSPACE software would
> support the standard behaviour. This does not appear to be the case.  There
> are two ways to deal with this:
>
>    1. change DSPACE to treat  If-Last-Modified-Since in the usual manner
>    2. cache data, as you say
>
> I am not a web server guru and would be thankful if you could give me some
> pointers on ow to set caching up correctly for DSPACE instances using
> Apache
>
> Monika
>
> .......
> Monika Mevenkamp
> Lead Software Engineer, Educopia Institute / MetaArchive Cooperative
>
> http://tinyurl.com/mevenkamp
>
>
> On Thu, Nov 29, 2012 at 8:45 AM, João Melo <[email protected]> wrote:
>
>> Hi Monika,
>>
>> I wasn't able to understand your issue, why are you sending HTTP requests
>> with response parameters? They trigger no action from the server, at least
>> they would trigger an error.
>>
>> I don't know which http server is being used within those request
>> examples, but the Expires HTTP header is commonly inactive by default,
>> basically the server could use some caching mechanism for subsequent
>> responses or not, seems like one of them supports cache, and the other one
>> does not.
>>
>>
>> On 27 November 2012 17:11, Monika Mevenkamp <[email protected]> wrote:
>>
>>> Looking at several DSPACE instance I see the following behaviour
>>>
>>> wget -S   <abitstream>
>>>      gets the bistream - shows the last modfified date
>>> wget -S --header  '"Last-Modified of bitstream + 1  day'
>>>     gets the bistream - although the given date is 1 day later than the
>>> bitstream's last modified
>>>
>>> In one example instance I see an Expires header that matches the current
>>> time
>>> In another example Last-Modified doesn't seem to trigger a 'short'
>>> response even though there is no Expires header
>>>
>>> How can this be fixed ?
>>>
>>> Monika
>>>
>>>
>>> Here two actual examples:
>>>
>>> Expires header in response:
>>>
>>> wget -S --header "Last-Modified: Mon, 20 Mar 2006 10:14:50 GMT" '
>>> http://ir.library.oregonstate.edu/xmlui/bitstream/handle/1957/1337/SteveStarcevichThesisText.pdf?sequence=1
>>> '
>>> --2012-11-27 11:25:01--
>>>
>>> http://ir.library.oregonstate.edu/xmlui/bitstream/handle/1957/1337/SteveStarcevichThesisText.pdf?sequence=1
>>> Resolving ir.library.oregonstate.edu <http://ir.library.oregonstate.edu>
>>> (ir.library.oregonstate.edu <http://ir.library.oregonstate.edu>)...
>>> 128.193.164.207
>>> Connecting to ir.library.oregonstate.edu
>>> <http://ir.library.oregonstate.edu> (ir.library.oregonstate.edu
>>> <http://ir.library.oregonstate.edu>)|128.193.164.207|:80... connected.
>>>
>>> HTTP request sent, awaiting response...
>>>    HTTP/1.1 200 OK
>>>    Date: Tue, 27 Nov 2012 16:25:01 GMT
>>>    Server: Apache/2.2.15 (CentOS)
>>>    Set-Cookie: JSESSIONID=185239DA0AE43D7B68997ED7D6E1EA5E; Path=/xmlui
>>>    X-Cocoon-Version: 2.2.0
>>>    Vary: User-Agent
>>> *  Last-Modified: Sun, 19 Mar 2006 10:14:50 GMT*
>>> *  Expires: Tue, 27 Nov 2012 17:25:01 GMT*
>>>
>>>    Content-Length: 165582
>>>    Connection: close
>>>    Content-Type: application/pdf
>>> Length: 165582 (162K) [application/pdf]
>>> Saving to: `SteveStarcevichThesisText.pdf?sequence=1.1'
>>>
>>> 100%[======================================>] 165,582      355K/s   in
>>> 0.5s
>>>
>>> 2012-11-27 11:25:02 (355 KB/s) -
>>> `SteveStarcevichThesisText.pdf?sequence=1.1' saved [165582/165582]
>>>
>>>
>>> Example without Expires
>>>
>>> wget -S --header "Last-Modified: Thur, 05 Jun 2008 15:48:31 GMT" '
>>> http://archive.nyu.edu/bitstream/2451/27463/2/SSRN-id143108.pdf'
>>> --2012-11-27 11:30:00--
>>> http://archive.nyu.edu/bitstream/2451/27463/2/SSRN-id143108.pdf
>>> Resolving archive.nyu.edu <http://archive.nyu.edu> (archive.nyu.edu
>>> <http://archive.nyu.edu>)... 128.122.108.89 <tel:128.122.108.89>
>>> Connecting to archive.nyu.edu <http://archive.nyu.edu> (archive.nyu.edu
>>> <http://archive.nyu.edu>)|128.122.108.89 <tel:128.122.108.89>|:80...
>>>
>>> connected.
>>> HTTP request sent, awaiting response...
>>>    HTTP/1.1 200 OK
>>>    Date: Tue, 27 Nov 2012 16:30:00 GMT
>>>    Server: Apache/2.2.9 (Unix) mod_jk/1.2.26 mod_ssl/2.2.9 OpenSSL/0.9.7d
>>>    Set-Cookie: JSESSIONID=19AF7C000ED11486D99A8BF7AE7BCC6A; Path=/
>>> *  Last-Modified: Wed, 04 Jun 2008 15:48:31 GMT*
>>>
>>>    Content-Length: 426332
>>>    Keep-Alive: timeout=5, max=100
>>>    Connection: Keep-Alive
>>>    Content-Type: application/pdf
>>> Length: 426332 (416K) [application/pdf]
>>> Saving to: `SSRN-id143108.pdf.7'
>>>
>>> 100%[======================================>] 426,332     2.17M/s   in
>>> 0.2s
>>>
>>> 2012-11-27 11:30:00 (2.17 MB/s) - `SSRN-id143108.pdf.7' saved
>>> [426332/426332]
>>>
>>> .......
>>> Monika Mevenkamp
>>> Lead Software Engineer, Educopia Institute / MetaArchive Cooperative
>>>
>>> http://tinyurl.com/mevenkamp
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Monitor your physical, virtual and cloud infrastructure from a single
>>> web console. Get in-depth insight into apps, servers, databases, vmware,
>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>> Pricing starts from $795 for 25 servers or applications!
>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>> _______________________________________________
>>> DSpace-tech mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>>
>>>
>>
>>
>> --
>> Thanks, João Melo (My Portfolio <http://www.lyncode.com/m/jmelo/>)
>> DSpace Department
>> *Lyncode*: Official 
>> website<http://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2F&sa=D&sntz=1&usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ>
>> [image: Follow us on 
>> Facebook]<http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q>
>> <http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww>
>>
>>
>
>
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel:
> VERIFY Test and improve your parallel project with help from experts
> and peers. http://goparallel.sourceforge.net
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>



-- 
Thanks, João Melo (My Portfolio <http://www.lyncode.com/m/jmelo/>)
DSpace Department
*Lyncode*: Official
website<http://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2F&sa=D&sntz=1&usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ>
[image: Follow us on
Facebook]<http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q>
<http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww>
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
VERIFY Test and improve your parallel project with help from experts 
and peers. http://goparallel.sourceforge.net
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to