You may do so using the Session::flash method:. When using the database session driver, you will need to setup a table to contain the session items. Below is an example Schema declaration for the table:. Of course, you may use the session:table Artisan command to generate this migration for you! The session "driver" defines where session data will be stored for each request. Laravel ships with several great drivers out of the box:.
Note: The array driver is typically used for running unit tests , so no session data will be persisted. Please see Configuring Session Cookies for more information. As the data are just kept for the next request and because there are no guarantees to ensure the request order in a complex Web application, the Flash scope is subject to race conditions. So for example, after saving an item, you might want to redirect the user back to the index page, and you might want to display a message on the index page saying that the save was successful.
In the save action, you would add the success message to the flash scope:. Then in the index action, you could check if the success message exists in the flash scope, and if so, render it:. Found an error in this documentation? The source code for this page can be found here. After reading the documentation guidelines , please feel free to contribute a pull request. Data stored in the session using this method will be available immediately and during the subsequent HTTP request.
After the subsequent HTTP request, the flashed data will be deleted. Flash data is primarily useful for short-lived status messages:. If you need to persist your flash data for several requests, you may use the reflash method, which will keep all of the flash data for an additional request.
If you only need to keep specific flash data, you may use the keep method:. To persist your flash data only for the current request, you may use the now method:. The forget method will remove a piece of data from the session. If you would like to remove all data from the session, you may use the flush method:. Regenerating the session ID is often done in order to prevent malicious users from exploiting a session fixation attack on your application.
Laravel automatically regenerates the session ID during authentication if you are using one of the Laravel application starter kits or Laravel Fortify ; however, if you need to manually regenerate the session ID, you may use the regenerate method:. If you need to regenerate the session ID and remove all data from the session in a single statement, you may use the invalidate method:.
Currently, those cache drivers include the memcached , dynamodb , redis , and database drivers. In addition, you may not use the cookie session driver. By default, Laravel allows requests using the same session to execute concurrently.
For many applications, this is not a problem; however, session data loss can occur in a small subset of applications that make concurrent requests to two different application endpoints which both write data to the session. To mitigate this, Laravel provides functionality that allows you to limit concurrent requests for a given session.
To get started, you may simply chain the block method onto your route definition. The block method accepts two optional arguments. The first argument accepted by the block method is the maximum number of seconds the session lock should be held for before it is released. Of course, if the request finishes executing before this time the lock will be released earlier. The second argument accepted by the block method is the number of seconds a request should wait while attempting to obtain a session lock.
If neither of these arguments is passed, the lock will be obtained for a maximum of 10 seconds and requests will wait a maximum of 10 seconds while attempting to obtain a lock:. If none of the existing session drivers fit your application's needs, Laravel makes it possible to write your own session handler. This interface contains just a few simple methods. A stubbed MongoDB implementation looks like the following:.
0コメント