Inconsistent parameter naming between Storage::fake temporary URLs (expiration) and signed routes (expires) #55446
Unanswered
moessimple
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I noticed an inconsistency between how temporary signed URLs are generated when using
Storage::fake()
in tests versus how they are built in production usingStorage::temporaryUrl()
orURL::signedRoute()
.In tests (
Storage::fake()
)When faking a disk and building a temporary URL, the parameter expiration is used:
In production (
URL::signedRoute()
)However, the signedRoute() method adds the expiration using the
expires
parameter:This means that in tests, URLs will contain
expiration=
..., while in production, they containexpires=
Is this difference in parameter naming intentional?
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions