Aaanndd ofcourse it was due to the proxy settings…

I noticed that the history refresh is done through a call of the API and since I had re-routed that to a different web server than the main server, it broke…

But once I added this rewrite rule:

ReWriteRule ^(/api/histories/.*) http://localhost:8080$1 [P,L]

Before the other /api/ one, the refresh of the history worked again…

It seems I need to spend a little more time on this whole proxy setting thing…

Thon

From: galaxy-dev-bounces@lists.bx.psu.edu [mailto:galaxy-dev-bounces@lists.bx.psu.edu] On Behalf Of Thon de Boer
Sent: Thursday, February 14, 2013 10:58 PM
To: 'Galaxy-dev Galaxy-dev'
Subject: Re: [galaxy-dev] History does not automatically update anymore

I do now actually get an error message in my browser saying “Error getting history updates from the server. Internal Server Error”

Any ideas?

I suspect it is my proxy server settings but not sure…

Thon

From: galaxy-dev-bounces@lists.bx.psu.edu [mailto:galaxy-dev-bounces@lists.bx.psu.edu] On Behalf Of Anthonius deBoer
Sent: Thursday, February 14, 2013 2:31 PM
To: Galaxy-dev Galaxy-dev
Subject: [galaxy-dev] History does not automatically update anymore

Hi,

I have noticed that in the latest version of galaxy-dist, my history does not automatically update anymore.

I have to press the refresh circle to have it update...

I did change my proxy setup a little, so it would no longer require API calls to be authenticated, while access through the frontend would still require that so it may have something to do with that, but just wanted to check if others see this issue...

I will send out my proxy settings in a later email, since it may help people that are struggling with the same...

Thon