URI From Incoming Request Always Returns '/' On Octane

[otezz]

Hi,

I'm currently trying to apply an only filter using the pattern '/v1*' for incoming requests, but it's not working as expected.

After some investigation, I discovered that the uri from incoming requests always returns '/' when the application is running under Octane. This issue only occurs in our cloud environment, where the app is deployed on AWS ECS. Octane is running on port 8000, and traffic is routed through an AWS ELB to the containers.

This filtering works perfectly in the local environment when running the app using php artisan serve. I also found that the uri values stored in our database are correct (We store Clockwork data to a MySQL table).

Would appreciate any insight or suggestions on how to ensure the correct URI is preserved and made available to Laravel Octane.

Thanks!

[itsgoingd]

Hey, where is the dump from first screenshot coming from?

We use exactly the same api (Request::getRequestUri) for both the should-collect checking and for the collected URI field in metadata, so it doesn't make much sense to have two different values. I also couldn't reproduce this issue with Octane running locally so far.