Jess Archer

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Thanks for the PR, and I'm sorry for the delay! I've merged #592 which should address this issue without adding the scheme and host, which may be a breaking change...

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel to open up a new issue if you're still experiencing this problem.

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Hi, this should be addressed by #592. Sorry for the delay!

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

I believe this was solved in #333, although that potentially introduced another bug (https://github.com/inertiajs/inertia-laravel/issues/359). Note that in addition to configuring the trusted proxy, the `X_FORWARDED_PREFIX` header has to be allowed...