Re: help with upgrade -- CSRF / Redback / proxy

Maybe we should rewrite the configuration as it's a mix of legacy properties xml etc... I guess it's not really clear :-) Maybe for 3.0.0? On 1 June 2017 at 15:20, Martin Stockhammer wrote: > Hi, > > it is mentioned in the release notes. But not clear enough, I think. I >

Re: help with upgrade -- CSRF / Redback / proxy

Hi, it is mentioned in the release notes. But not clear enough, I think. I will improve the docs. Greetings Martin Am 1. Juni 2017 05:02:14 MESZ schrieb Adam Brin : >Martin, >Thank you, that really helped. It might be nice to identify some of >this >in the upgrade

Re: help with upgrade -- CSRF / Redback / proxy

Martin, Thank you, that really helped. It might be nice to identify some of this in the upgrade notes for 2.2.3, I definitely missed all of this when I went to try and figure out what was broken. - adam On Wed, May 31, 2017 at 1:15 PM, Martin wrote: > Yes, thats the

Re: help with upgrade -- CSRF / Redback / proxy

Yes, thats the right place to configure it. redback properties have been moved to archiva.xml Inside the ... Element. This section is also changed, when you change the Redback Runtime properties by the WebUI:

Re: help with upgrade -- CSRF / Redback / proxy

I had same problem when I upgarded archiva, issue was fixed by adding rest.baseUrl in archiva.xml and restart archiva rest.baseUrl=.https://dev.server.com/archiva On Wed, May 31, 2017 at 2:35 PM, Adam Brin wrote: > Hi, > We

help with upgrade -- CSRF / Redback / proxy

Hi, We proxy our archiva install behind nginx such that https://dev.server.com/archiva/ —> http://localhost:9/ . I’ve been trying to read the documentation on how to update, but I’m afraid, I’m a bit lost. A few questions: Where is the redback config stored, is it in