single_use and deactivated_at

[khalidzaibi]

https://vimeo.com/748255348/fee77b1371

the above recorded for proof.
I have add two things
1- single use only
2-deactivaed_at
both are not working properly, you can see in the video single use only for 1 but i can open same link again and again.
and in the next the deactivated time is expire but link open and working

I need in this package the expired link remove automatically.

[khalidzaibi]

There is one thing more that i have notice that is Cache, I have create a middleware for remove deactivated links and it's work fine that remove all links are expired but when i hit the copied link again it's showing the same result what you think about it.
I want to show public directory file of destination url.

[ash-jc-allen]

Hey! Sorry to hear that you're having problems with the package.

From looking at your video, it looks like your short URLs have a 301 redirect status code? Is that right?

If so, this could be the reason for your activation times and single-use links not working. If your web browser is redirected with a 301 status code, then it'll treat it as a permanent redirect. This means that next time you visit your short URL, your browser will automatically redirect you to the destination URL without hitting your server. This means that we can't handle the redirect in the Laravel app to make sure that it's still valid.

If you create your short URLs with a 302 status code instead, the browser will treat this as a temporary redirect. This means that when you visit it, your browser will go to your Laravel app as intended and we can then handle the redirect ourselves.

Do you still have this error if you create a new short URL with a 302 status code? 🙂

[khalidzaibi]

Hey! Sorry to hear that you're having problems with the package.

From looking at your video, it looks like your short URLs have a 301 redirect status code? Is that right?

If so, this could be the reason for your activation times and single-use links not working. If your web browser is redirected with a 301 status code, then it'll treat it as a permanent redirect. This means that next time you visit your short URL, your browser will automatically redirect you to the destination URL without hitting your server. This means that we can't handle the redirect in the Laravel app to make sure that it's still valid.

If you create your short URLs with a 302 status code instead, the browser will treat this as a temporary redirect. This means that when you visit it, your browser will go to your Laravel app as intended and we can then handle the redirect ourselves.

Do you still have this error if you create a new short URL with a 302 status code? 🙂

Actually I handled this issue with different way e.g i add key with destination url and at time of hit check first check key of destination url and move forward.
Please consider my next question how to expire link remove automatically and if set
'tracking' => [
'default_enabled' => false,
]
why it save null value into this short_url_visits

[ash-jc-allen]

Hey! I'm glad that you managed to sort your issue.

Please could you open a new discussion for your other question? It helps for if there are other people with the same problem 🙂