Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Implement Vulcain directly in API Platform Core

Open
#5,884 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php

Research direction

Start by reviewing the API Platform providers and the existing "property" filter, since the issue identifies them as the relevant entry points. Done would mean Vulcain-style early hints and filtering are implemented directly in API Platform Core, but the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Description

The API Platform distribution has been including the Vulcain Gateway server for some time now.
Since API Platform 3.2, the API Platform distribution also uses FrankenPHP, which allows the HTTP status code "103 Early Hints" to be used directly from PHP.

Although the Vulcain Gateway server now supports the sending of 103 Early Hints in addition to HTTP/2 Server Push, this is almost useless do that in the gateway server: the Gateway server must retrieve the full JSON response from the upstream PHP server before it can calculate which resources to send. If the response is already in the cache of a reverse proxy, sending 103 is useless (the final response containing Preload hints added by the gateway server will be sent immediately). Otherwise, the proxy will have to wait for the JSON to be generated by the PHP server before calculating the 103 links, so we're in the same situation.

What would be better - in case the response is not already in the reverse proxy cache - would be for the PHP server to send the 103 response as soon as possible: ideally, in Platform API providers, when the data has been retrieved from the persistence layer, but before serialization generation (which is known to be a tedious task).

In addition to preloading, it would be interesting to also implement the filtering part of Vulcain (building on the existing "property" filter). This would not be very useful for responses that can be cached (it's better to store the complete response in the cache, and let the proxy do the filtering), but it will prevent some useless work when the response isn't cacheable.

Dominant language
PHP
Stars
2.6k
Forks
989
Avg merge
1d 23h
Merged PRs (30d)
102

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from api-platform/core

All issues in api-platform/core

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.