These are chat archives for spring-cloud/spring-cloud

3rd
Jun 2015
Ryan Baxter
@ryanjbaxter
Jun 03 2015 00:07
yeah was thinking of trying that as well
Ryan Baxter
@ryanjbaxter
Jun 03 2015 00:22
does the ${vcap.services.servicename.credentials.uri:http://…} syntax in yml files work in plain spring boot apps as well?
or that something specific to spring cloud?
Ryan Baxter
@ryanjbaxter
Jun 03 2015 01:01
nm i tested it out, the answer is it works! :)
Leon Radley
@leon
Jun 03 2015 12:17
Hmm I’m having troubles with zuul and angular, it’s creating a new session for me for every request.
It seems to not only be angular that is having troubles, if I call the url directly from the browser, it still creates a new session.
but and that means that it redirects to /login and then redirects to the login server and comes back…
very strange
Dave Syer
@dsyer
Jun 03 2015 13:22
Do you have 2 apps in localhost again?
Leon Radley
@leon
Jun 03 2015 13:24
hehe, yes I still do. but they have different session cookie names
do you think there is something with that causing them to collide?
Hmm very strange. the request was sent by angular directly in a controller. If I set a $timeout and wait 1sek before calling the proxy the request goes through fine
Dave Syer
@dsyer
Jun 03 2015 13:28
That does sound odd. Are you doing something else in the angular startup?
Setting interceptors, headers etc?
Leon Radley
@leon
Jun 03 2015 13:29
If I call the zuul url to tight together with the initial request, the zuul request tries to create a new session
no interceptors, and this header $httpProvider.defaults.headers.common['X-Requested-With'] = 'XMLHttpRequest’;
Dave Syer
@dsyer
Jun 03 2015 13:29
You have a race between 2 threads on the client?
Leon Radley
@leon
Jun 03 2015 13:31
Think I found something, one of the requests before is returning a Set-Cookie… investigating
The app in question is a sso app and a resource server app
I remove all the cookies and login
first the /login sets the cookie and redirect to the start page
everythings fine
up until I call the first resource server url, that returns a set-cookie