zgordon01 / GoalMind

2 stars 0 forks source link

known issue with profile pictures hitting our api and getting rejected #6

Closed zgordon01 closed 7 years ago

zgordon01 commented 7 years ago

capture

jacobtarter commented 7 years ago

Weird, I'm assuming you can add an exception to the middleware, basically the same way you're doing for the user route?

jacobtarter commented 7 years ago

I'm pretty sure any request at all other than the base localhost/ route will have to go through that middleware. If you type in localhost/(anything) you will get a 401

zgordon01 commented 7 years ago

The problem isn't that it's getting rejected... but I have no idea why it's hitting our api.. it shouldn't be

jacobtarter commented 7 years ago

yeah, that's strange. I just checked and if I log in with facebook I get my profile picture fine but I also get the error. where's the code that sets up the profile picture?

zgordon01 commented 7 years ago

it's in index.html. I'm not looking right now but it's in a ternary operator

zgordon01 commented 7 years ago

although this is an issue it really doesn't matter. The profile picture is pulled from the providers (facebook, google) not sure why it's hitting our api as well.

zgordon01 commented 7 years ago

I sent an email to some people at my job about this... I'll see if they can help figure this out

zgordon01 commented 7 years ago

fixed by using ng-src instead of src