没有不值得去解决的问题,也没有不值得去学习的技术!

In Laravel 6, Accessing https://object.local Redirects With a 302 to https://xxx.xxx.xxx.top

In Laravel 6, accessing https://object.local results in a 302 redirect to https://xxx.xxx.xxx.top

1. In Laravel 6, accessing https://object.local results in a 302 redirect to https://xxx.xxx.xxx.top. See Figure 1.

In Laravel 6, accessing https://object.local results in a 302 redirect to https://xxx.xxx.xxx.top
Figure 1

2. Searching for xxx.xxx.xxx.top in the source code yields no results. Additionally, all instances of xxx.xxx.xxx.top in the database have been replaced with object.local.

3. A key named laravel_cache:main_domain_cache exists in Redis, with the value: s:26:”xxx.xxx.xxx.top”;. See Figure 2.

A key named laravel_cache:main_domain_cache exists in Redis, with the value: s:26:"xxx.xxx.xxx.top";
Figure 2

4. After clearing Redis, accessing https://object.local again returns a 500 response. No 302 redirect occurs. This is the expected behavior. See Figure 3.

After clearing Redis, accessing https://object.local again returns a 500 response. No 302 redirect occurs. This is the expected behavior
Figure 3

关于作者 · 持续学习与技术实践

我是一名拥有 15 年以上开发经验的技术从业者,自 2013 年起持续运营个人技术博客,记录工作与个人项目中遇到的真实问题,以及解决问题过程中的探索、实践和思考。

除了技术写作,我也在持续开发和维护自己的独立项目,探索新技术和新工具在实际场景中的应用。我始终相信,没有不值得去解决的问题,也没有不值得去学习的技术。

如果这篇文章对你有所帮助,欢迎浏览博客中的其他文章,也欢迎交流技术经验与想法。

关于我  ·  GitHub  ·  邮件联系