date:20170207

Re: [dspace-tech] I have encountered errors while harvesting Data

2017-02-07 Thread Claudia Jürgen


Hi David,

could you provide more details, the version with which you are working
and error logs.
This might be related to:
https://jira.duraspace.org/browse/DS-2847

Hope this helps

Claudia Jürgen


Am 07.02.2017 um 07:51 schrieb david john:

I have encountered errors while harvesting data from other repositories
because the url is not encoded hence result in errors being displayed



--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] REST returns a bitstream as an attachment

2017-02-07 Thread Evgeni Dimitrov

This is about DSpace 5.6.
I noticed only now that when I request in the browser a bitstream -
something like

http://xxx.xxx.xxx/rest/bitstreams/n/retrieve

then the browser gets it with

Content-Disposition: "attachment; filename="img_01.jpg""

I remember there is something about JSPUI and XMLUI
webui.content_disposition_threshold
xmlui.content_disposition_threshold

but here it is about REST. Is there a way to tell rest to return the
bitstream inline?

Best regards
Evgeni

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] DSpace5 + nginx results in too many redirects.

2017-02-07 Thread Anis

Hey!

I'm setting up a dspace 5 instance using nginx. The problem I'm facing now 
is, that after going to the login page and clicking login I get "server 
redirected you too many times" error from my browser (Chrome on Mac OS). So 
the site works fine before I try to login, after that it gives the 
aforementioned error and only clearing cookies will get rid of it. Any 
ideas for fixing this?


ROOT.xml in the Catalina folder





nginx configuration (ommited some information)

server {
listen 80;
listen [::]:80;


server_name ;


return 301 https://$request_uri;
}
server {
listen 443 ssl;
listen [::]:443 ssl;


server_name ;


ssl_certificate ;
ssl_certificate_key ;
ssl_session_timeout 1d;
ssl_session_cache shared:SSL:50m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers 
'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'
;
ssl_prefer_server_ciphers on;


add_header Strict-Transport-Security max-age=15768000;



# forward everything to tomcat
location / {
proxy_pass ;
proxy_redirect  off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https;


client_max_body_size10m;
client_body_buffer_size 128k;


proxy_connect_timeout 120;
proxy_send_timeout 120;
proxy_read_timeout 120;


proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
}
}

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: ant fresh_install vs postgres

2017-02-07 Thread Walter Rutherford

*Sorry if this post is a bit chatty, but I wanted it to be helpful to 
anybody else who runs into the same problems.*

I had some initial success and was able to complete the 'ant 
fresh_install'. Tomcat didn't display the default page but
I think that may be because I installed it with yum rather than from source 
code like the manual expected and it was
installed in a different directory than DSpace expected. In the end I 
copied the directory ant built to where tomcat
expects to find its pages (symlinks didn't work) and tomcat started with 
the default page.

But it doesn't connect to the postgres database. That may be because it's 
running from a new location or there's still
and issue with the pg_hba.conf file. I tried connecting again as a 
different user as Tom suggested above and got a
new error:
  [walter@irtest ~]$ psql -h localhost -p 5432 -d dspace -U dspace
  psql: FATAL:  no pg_hba.conf entry for host "::1", user "dspace", 
database "dspace", SSL off

It looks like it has skipped over the IPv4 host md5 rule and is trying to 
connect via IPv6. We aren't actively using IPv6 but
just as a sanity check I added a new rule to the pg_hba.conf file:
  host dspace  dspace  ::1/128 md5

Then logged in as a different user. It worked. So why is it ignoring the 
nearly identical IPv4 host rule???
  host dspace dspace 127.0.0.1  255.255.255.255md5

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] invalid 301 Location: header

2017-02-07 Thread Tim Donohue

Hi George,

I think this issue is related to some (old) code that tried to keep the
XMLUI "compatible" with JSPUI-style URLs (to ease migration between the two
UIs). Specifically, these redirects of JSPUI-style paths to the
corresponding XMLUI ones:
https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/src/main/webapp/sitemap.xmap#L362

It sounds like it might be a bug here, but it's likely very infrequently
occurring. The XMLUI itself doesn't use URLs to bitstreams that look like
this: "/bitstream/[prefix]/[suffix]/[sequence]/[filename]" (That's a JSPUI
URL pattern). Instead, the XMLUI uses URLs to bitstreams that look like
this: "/bitstream/[prefix]/[suffix]/[filename]?sequence=[sequence]".

So, long story short, there may be a way to clean this up and fix it for
filenames with spaces. However, it likely won't be encountered unless you
move from JSPUI to XMLUI, and your users have bookmarked or saved the old
URLs (and one or more includes filenames with spaces).

- Tim

On Mon, Feb 6, 2017 at 1:23 PM George Kozak wrote:

We are running DSpace 5.5 (XMLUI with modified MIrage 2 theme).
I received an email today from someone on our campus that is running a link
checker. They got the following error when trying to download one of our
DSpace PDFs: "invalid 301 Location: header"

The URL that they used was:
curl -v
https://ecommons.cornell.edu/bitstream/1813/2094/1/Stanton%20Agr%20Econ%20History%20online.pdf

The PDF in question had spaces which was causing the error. We have always
urged our users not to put spaces or special characters in the filenames
that they upload, because we know that this causes some problems with
certain browsers, but this was the first time that someone told us that
these filenames were causing errors with link checkers.

The person who contacted me believes this is a bug in DSpace, but I'm not
so sure. I think this is pretty much how things have been since
DSpace1.0. Should this be considered a bug?

Does anyone know of a way to force users to submit filenames without spaces
or special characters?
--
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924 <(607)%20255-8924>
g...@cornell.edu

--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] invalid 301 Location: header

2017-02-07 Thread George Kozak

Thanks, Tim:
Yes, we moved from JSPUI to XMLUI a couple of years ago, but, of course,
people have book marked the old JSPUI paths to the bitstreams.
I guess I will deal with this on a one-by-one basis.  It only happens when
there are filename with spaces.
Thanks, again.
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924 <(607)%20255-8924>
g...@cornell.edu

On Tue, Feb 7, 2017 at 2:29 PM, Tim Donohue  wrote:

> Hi George,
>
> I think this issue is related to some (old) code that tried to keep the
> XMLUI "compatible" with JSPUI-style URLs (to ease migration between the two
> UIs). Specifically, these redirects of JSPUI-style paths to the
> corresponding XMLUI ones:
> https://github.com/DSpace/DSpace/blob/master/dspace-
> xmlui/src/main/webapp/sitemap.xmap#L362
>
> It sounds like it might be a bug here, but it's likely very infrequently
> occurring. The XMLUI itself doesn't use URLs to bitstreams that look like
> this: "/bitstream/[prefix]/[suffix]/[sequence]/[filename]" (That's a
> JSPUI URL pattern).  Instead, the XMLUI uses URLs to bitstreams that look
> like this: "/bitstream/[prefix]/[suffix]/[filename]?sequence=[sequence]".
>
> So, long story short, there may be a way to clean this up and fix it for
> filenames with spaces. However, it likely won't be encountered unless you
> move from JSPUI to XMLUI, and your users have bookmarked or saved the old
> URLs (and one or more includes filenames with spaces).
>
> - Tim
>
> On Mon, Feb 6, 2017 at 1:23 PM George Kozak  wrote:
>
> We are running DSpace 5.5 (XMLUI with modified MIrage 2 theme).
> I received an email today from someone on our campus that is running a link
> checker.  They got the following error when trying to download one of our
> DSpace PDFs: "invalid 301 Location: header"
>
> The URL that they used was:
> curl -v https://ecommons.cornell.edu/bitstream/1813/2094/1/
> Stanton%20Agr%20Econ%20History%20online.pdf
>
> The PDF in question had spaces which was causing the error.  We have
> always urged our users not to put spaces or special characters in the
> filenames that they upload, because we know that this causes some problems
> with certain browsers, but this was the first time that someone told us
> that these filenames were causing errors with link checkers.
>
> The person who contacted me believes this is a bug in DSpace, but I'm not
> so sure.  I think this is pretty much how things have been since
> DSpace1.0.  Should this be considered a bug?
>
> Does anyone know of a way to force users to submit filenames without
> spaces or special characters?
> --
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924 <(607)%20255-8924>
> g...@cornell.edu
>
> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
> --
>
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
>


-- 
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
g...@cornell.edu

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Dspace 5.6 Workflow Issue

2017-02-07 Thread James Holobetz

I am experiencing the https://jira.duraspace.org/browse/DS-2920 problem and
was wondering if anyone had an idea how to fix the issue.

Is this the fix?

Marie-Helene Vézina
 added
a comment - 16/Dec/15 1:39 PM - edited

The workaround we found (at least for now) is to force DSpace to look into
the database instead of using the cache. Doing so doesn't throw an error.

So in file:

[Source]\dspace-api\src\main\java\org\dspace\workflow\WorkflowItem.java

We have added one more line:

public static WorkflowItem find(Context context, int id)
throws SQLException
{
// First check the cache
WorkflowItem fromCache = (WorkflowItem) context.fromCache(
WorkflowItem.class, id);

fromCache = null; // <= this forces Dspace not to use the cache

if (fromCache != null)
{   return fromCache;  }

(...)

I don't know if intervening with the cache is the right approach to solve
this problem but it seems to work for us.



James

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] I have encountered errors while harvesting Data

[dspace-tech] REST returns a bitstream as an attachment

[dspace-tech] DSpace5 + nginx results in too many redirects.

[dspace-tech] Re: ant fresh_install vs postgres

Re: [dspace-tech] invalid 301 Location: header

Re: [dspace-tech] invalid 301 Location: header

[dspace-tech] Dspace 5.6 Workflow Issue

7 matches

Site Navigation

Mail list logo

Footer information