kandi X-RAY | XBackBone Summary
kandi X-RAY | XBackBone Summary
XBackBone is a simple, self-hosted, lightweight PHP file manager that support the instant sharing tool ShareX and *NIX systems. It supports uploading and displaying images, GIF, video, code, formatted text, and file downloading and uploading. Also have a web UI with multi user management, past uploads history and search support.
Top functions reviewed by kandi - BETA
- Upgrade package .
- Load file with file sort .
- Login to LDAP server .
- Show media .
- Update user .
- Register a new user .
- Migrate migrations .
- Home page .
- Connect to LDAP server .
- Recover the mail .
XBackBone Key Features
XBackBone Examples and Code Snippets
Trending Discussions on XBackBone
I'm experiencing a problem using HTTP/2 push preload with the php session: when I open a page that use a preload header feature, the session is lost/reset. The application code is open source, here is where I set the Link header: https://github.com/SergiX44/XBackBone/blob/master/app/Controllers/UploadController.php#L107...
ANSWERAnswered 2018-Nov-19 at 21:54
In Apache HTTP/2 module only certain headers are copied on pushed request.
The full list of headers is listed in the Apache documentation
Apache will look at the original request (the one that triggered the PUSH) and copy the following headers over to PUSH requests:
user-agent, accept, accept-encoding, accept-language, cache-control.
All other headers are ignored. Cookies will also not be copied over. PUSHing resources that require a cookie to be present will not work. This can be a matter of debate. But unless this is more clearly discussed with browser, let's err on the side of caution and not expose cookie where they might oridinarily not be visible.
Note how it explicitly calls out that cookies will not be sent. Therefore there is no session and so your PHP app is setting a new one.
HTTP/2 push is intended to send safe, cacheable resources and Apache has chosen to interpret this has non-authenticated resources. Therefore unless you can serve your pushed resource without requiring cookies, you should not push it.
You can use the
preload header with the
nopush attribute to avoid pushing it, but still have the browser request it with high priority. As the browser is requesting it, it will send the appropriate cookies and all should work. It may not be quiet as fast as push but it’s often good enough. Additionally as browsers are aware of their cache, using preload instead of push is often recommended anyway. Push is complicated to get right - and not just because of the issue you’ve spotted here.
No vulnerabilities reported
PHP requires the Visual C runtime (CRT). The Microsoft Visual C++ Redistributable for Visual Studio 2019 is suitable for all these PHP versions, see visualstudio.microsoft.com. You MUST download the x86 CRT for PHP x86 builds and the x64 CRT for PHP x64 builds. The CRT installer supports the /quiet and /norestart command-line switches, so you can also script it.
Reuse Trending Solutions
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page