- Is srio/rest-upload-bundle compatible with Laravel?
- No. srio/rest-upload-bundle is a Symfony bundle built for Symfony 2.x/3.x, and it depends on Symfony's kernel, dependency-injection compiler passes, event dispatcher, form component, and HttpFoundation. Laravel has no equivalent bundle model, so the package cannot be installed into a Laravel application in any meaningful way. If you are on Laravel, use native upload primitives instead.
- What does srio/rest-upload-bundle actually do?
- It provides a REST upload endpoint that accepts several payload conventions: multipart/form-data, base64-encoded files embedded in JSON, and chunked or partial PATCH-based uploads. It also wires uploaded files into Symfony forms so they can be bound to a domain object. The real value is the design pattern, not reusable Laravel code.
- How do I install srio/rest-upload-bundle?
- You would install it with Composer as a Symfony bundle and register it in the Symfony kernel, but this is only realistic on an old Symfony 2.x/3.x stack. There has been no release since September 2016, and Composer constraints will almost certainly refuse to resolve against PHP 8+ and Symfony 5/6/7. For any modern project you should fork and modernize it, or reimplement the pattern.
- Does srio/rest-upload-bundle support chunked or resumable uploads?
- Yes, the bundle supports chunked and partial uploads using PATCH-based resumption, which is one of its three payload conventions. However, the implementation predates modern PHP and Symfony releases and has not been maintained since 2016. In Laravel, use a maintained package such as pion/laravel-chunk-upload or a TUS-protocol implementation instead.
- Can srio/rest-upload-bundle accept base64-encoded files in JSON?
- Yes, one of its advertised modes embeds base64-encoded files inside JSON payloads. That approach inflates payload size by roughly 33 percent and tends to buffer the entire file in memory, so it is only defensible below a few megabytes. If you need this in Laravel, a small custom request class plus a streaming decoder gives you control over size limits and memory behavior.
- What PHP and Symfony versions does srio/rest-upload-bundle support?
- It was built for Symfony 2.x/3.x and predates Symfony 4's directory restructure, the configureOptions and getBlockPrefix form API changes, and every PHP 8.x release. No release has shipped since September 2016. Composer dependency resolution will almost certainly fail on PHP 8+ and Symfony 5/6/7.
- Is srio/rest-upload-bundle maintained and safe for production?
- No. The package has not shipped a release since September 2016, has 46 stars and zero dependents, and there is no upstream to notify about security issues. File upload handling is security-sensitive, covering MIME-type spoofing, path traversal via client-supplied filenames, memory-exhaustion attacks, and unbounded temp-storage growth from abandoned chunked uploads. An unmaintained package in this domain is a high technical risk.
- What should I use instead of srio/rest-upload-bundle in Laravel?
- Laravel already covers the multipart path natively with $request->file(), the file, mimes, and max validation rules, UploadedFile::storeAs(), and the filesystem abstraction with S3 or GCS disks. For resumable uploads, use an actively maintained package such as pion/laravel-chunk-upload or a TUS-protocol implementation. For base64-in-JSON, write a small custom request class with a streaming decoder rather than importing a legacy bundle.
- Can I use srio/rest-upload-bundle with Symfony 5, 6, or 7?
- Not without a fork and a nontrivial modernization pass. The bundle's extension points assume Symfony's form events and request lifecycle from the 2.x/3.x era, and its Composer constraints will almost certainly block installation on Symfony 5/6/7. On modern Symfony, prefer OneupUploaderBundle or VichUploaderBundle for file-to-entity mapping and a TUS implementation for resumption.
- How do I test a REST upload implementation if I reimplement the pattern?
- Treat the bundle's README and test suite as the specification for request and response shapes, content-type negotiation rules, and chunk-assembly semantics, then write your own feature tests against those contracts. In Laravel, use UploadedFile::fake() with storage fakes to cover multipart, base64, and chunked paths, and assert validation failures for oversized, spoofed, and malformed payloads. Include tests for abandoned chunk cleanup and path traversal protection.