- What does laravel-http-to-curl do?
- It is a Laravel diagnostic package that converts outbound HTTP client requests into ready-to-run cURL commands. You can use the generated command to inspect, debug, reproduce, and share API calls during development or support work. It is intended as a productivity tool for apps with outbound HTTP integrations, not as a core runtime dependency.
- How do I install laravel-http-to-curl in a Laravel app?
- Install it with Composer, typically via composer require jigarakatidus/laravel-http-to-curl. Laravel package auto-discovery should register the service provider with minimal application wiring. After installation, confirm the package is discovered and smoke-test a representative outbound request before adding it to team workflows.
- Which Laravel and PHP versions are supported by laravel-http-to-curl?
- Release 1.0.5 adds Laravel 13 support, and the package is designed for Laravel applications using the Http facade or Guzzle-backed outbound calls. The exact PHP and illuminate constraints should be checked in the package composer.json before upgrading. If your app stays on older Laravel versions, verify that the updated constraints still allow installation.
- Does laravel-http-to-curl work with Laravel 13?
- Yes, release 1.0.5 adds Laravel 13 support according to the release notes. Validate package discovery, macro availability, and generated cURL output in a development branch before relying on it in support workflows. Also confirm that Laravel 13 coverage exists in the maintainer test matrix or CI, not only in dependency constraints.
- How do I generate a cURL command from a Laravel HTTP client request?
- The package extends Laravel HTTP debugging so you can dump and die with a cURL command instead of only inspecting the request object. Use it around the HTTP client call you want to diagnose, then copy the generated command for reproduction. Exact method names and syntax should be confirmed against the package README for your installed version.
- Does the generated cURL command include Authorization headers and API keys?
- Generated cURL commands can include the same headers and payload data as the request, so Authorization headers, cookies, API keys, and signed URLs may appear in the output. The package context flags secret exposure as a primary risk, and redaction behavior must be verified for your version. Do not paste unredacted cURL commands into tickets, chat, or logs.
- How are JSON, form, multipart, and file upload requests represented in the cURL output?
- The package aims to represent the outbound request as a cURL command, but complex bodies such as multipart uploads and file uploads may not map perfectly to Laravel or Guzzle behavior. Test JSON, form, multipart, and error-case requests explicitly and compare the generated command with the actual request. Treat the cURL output as a diagnostic aid, not a byte-for-byte guarantee for every payload type.
- Can I use laravel-http-to-curl in production?
- It is best suited for local, staging, or support diagnostics rather than production runtime use. Generating cURL on every outbound request can add overhead and create sensitive-log exposure, so avoid logging it at scale. If used in production-adjacent environments, apply strict guardrails for secret handling and retention.
- Does it support async requests, retries, middleware, proxies, and custom Guzzle handlers?
- The generated cURL may not fully represent Laravel or Guzzle behavior for middleware, retries, async requests, TLS settings, proxies, or custom handlers. Those features can change the actual wire request in ways a static cURL command cannot capture. Validate representative cases and document limitations for your support runbooks.
- Is laravel-http-to-curl actively maintained, and what are alternatives?
- Release 1.0.5 adding Laravel 13 support is a positive maintenance signal for this small diagnostic package. Alternatives include Laravel built-in HTTP client dump and dd helpers, Guzzle middleware or logging, or manually reconstructing requests, but this package focuses on shareable cURL output. Track Laravel major-version compatibility and review the release diff before upgrades.