![]() In some cases, though, it is preferable not to abort the PHP script, regardless of whether the connection has been closed. This is to avoid wasting system resources and to prevent certain types of DoS attacks. When a user closes a connection (by closing a window, for example), LSWS will abort processing that PHP script by killing the PHP process. It explains in detail what noabort and noconntimeout do for long-running PHP scripts and how to implement them through different methods, if you wish. To learn more, read through the rest of this documentation. The narrower the scope, the less likely you will run into an issue. Apply it to a specific script URL instead of. We suggest you add noabort selectively, and only when absolutely necessary. This is because LSWS is not able to abort any external app requests. For example, a site running in a Cloudlinux Lightweight Virtual Environment (LVE) that is hitting resource limits can become completely tied up. htaccess is not standard practice and may cause unintended consequences. *), but we strongly suggest you do not do this.Īdding noabort for all requests to. We know it is tempting to simply add noabort for all requests (. LiteSpeed Memcached LiteSpeed Memcached.LSCache Developers Guide LSCache Developers Guide.LSCache Without a Plugin LSCache Without a Plugin. ![]() Third Party Plugins Third Party Plugins.Set LSAPI_MAX_PROCESS_TIME Environment Variable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |