Skip to content

HTTP service interceptors don't cover all network interactions. #53470

Open

Description

Kibana plugins use different HTTP clients in the browser. Besides fetch provided by the core, we have in the codebase:

  • axios - Canvas, Beats Management, Infra, Upgrade Assistant, Uptime, Telemetry
  • apollo - Infra, Siem, Uptime

While all other plugins (especially Security) relays on the fact that all network requests are done via fetch and could be intercepted for performing an additional logic (extend a user session, for example).

Things to discuss:

  • Is it possible to unify the network stack whenever possible?
  • If it's not possible to unify the network stack, should we make interceptors reusable for 3rd party network libraries?
  • Is the interceptor's mechanism scalable for Kibana case?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Feature:New PlatformTeam:CoreCore services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etcdiscuss

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions