API Auth & State via AJAX

Hey Stephane

Thanks for the info man! probably in a couple of years all browsers will do the same

Cheers!

Chromium 69... no errors too.

Excellent!

Hey @HimmelHempsted

Sorry for late answer! I think you should configure @MaxDepth() annotation, on your Entities, Not sure about you structure, you should try to add it to $books or $notes properties, try to play with it to get best result for your structure!

Cheers!

Hey Skylar

That's funny. How looks your controller's API endpoint?
When you get the profiler's html as response did the request fail?

Cheers!

When it fails, I look at the last 10 requests, and it is NOT in the list. But if I look the inspector tools in chrome, it shows that it was sent. I also added a random number to the query string to do cache busting in case that was a possibility.

Hmm, that's indeed weird. Which web server are you using? I believe there is something funny on your configuration

I am using the symfony server

Are you using a HTTPS connection? I don't really know what's going on but could you try starting your web server by running
bin/console server:start and try again?

So I solved my problem by replacing the Symfony Built-in server with apache using xampp. All the problems went away. So, my guess is that there must have been a timing issue using the built-in server. go figure.

Hmm, that's super weird. You should be able to run your Symfony app through Symfony web-server. Probably there is an issue related to something specific to your environment. I would try re-installing Symfony CLI but well... at least you can keep going on :)

Cheers!

Hey Johann I.

So, your browser is not executing any requests to "reps" endpoint? It is very likely that your application is not performing that requests on page load, i.e. on "componentDidMount" method. Double check that your app is indeed executing that request

Cheers!

Hey bartek!

It depends on what you want the behavior to be. The easiest solution would be to increase Symfony's session length, or use a "remember_me" cookie (you can even automatically turn this on) so that users are basically *not* logged out. Or, you could create a heartbeat AJAX request that is sent every 10 minutes to maintain a session with the server. Or, if you *do* want to allow people to be logged out, and you want present them with the login form, it's a bit tricker. You'll need to make sure that all of your AJAX/API calls go through a central function, and in that central function you'll call fetch(). You'll need to attach an error handler that looks for authentication failure (I would also make your authentication system return a 401 response + JSON when you need to login, at least if it detects if it's an AJAX request. How you do this depends on how you've built your authentication system) and then opens a React component to show the login page. You'll also need to "save" the original request details so that you can re-send them after success.

I know this is a very generic answer - but there are multiple ways to handle it depending on what you need :).

Cheers!

I thought about remember_me or error handler, thank you very much for your reply!

Hi! I have a question regarding this. You are saying to have a central function for all ajax request to check if user is authentificated. So authentification checking is done only when ajax call is made. What if I want also check if the session expired or not when I am not active on the page and its automatically redirects to login page? My login page is doen in React. Should I have a function to periodically check the session expired or not in may entry file App? Thanks in advance

Hey Assel N.

If you want to check if the session has expired or not at the front-end level, then yes, you will have to execute a function periodically. Now, the function doesn't have to live in the main App file, it depends on your structure but that's something you can re-arrange when the time comes.

Cheers!