Skip to content

Laravel: API client caching conflict with HTTP middleware #6

@francescobianco

Description

@francescobianco

Labels: bug, laravel, middleware
Context: Laravel 11 + HTTP Client middleware (Guzzle handler stack)

Description:
When using the Openapi SDK within a Laravel service, the built-in HTTP client middleware is bypassed. This prevents Laravel's retry() or cache() functionality from being applied to Openapi API calls.

Expected:
SDK should expose an option to inject a pre-configured Guzzle client or middleware stack.

Impact:
Loses consistency with Laravel's HTTP pipeline and prevents centralized caching of API responses.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions