CodeIgniter 的问题。部署时 DX_Auth 不起作用
因此，我们目前使用的是 CodeIgniter + DataMapper OverZealous Edition + DX Auth。它正在我们的本地计算机以及我们的临时服务器上运行。但是，一旦我们推送到他们的服务器，登录就根本不起作用。经过进一步调查，表单中的数据没有进入我们进行身份验证的控制器。我们已经取消了所有服务器端 CI 数据验证，但它仍然是空白的。
我们的临时服务器正在运行：
服务器 Apache/2.2.9 (Ubuntu) mod_fastcgi/2.4.6 mod_python/3.3.1 Python/2.5.2 mod_wsgi/2.3 PHP/5.2.6-2ubuntu4.5 和 Suhosin-Patch mod_ssl/2.2。 9 OpenSSL/0.9.8g X-Powered-By PHP/5.2.6-2ubuntu4.5
他们的服务器正在运行：
Server Apache/2.2.3 (CentOS) X-Powered-By PHP/5.2.9
我真的不想在第 11 个小时内放入不同的身份验证框架，我已经为这个项目通宵达旦了太多。有人有什么想法吗？？？
So we're currently using CodeIgniter + DataMapper OverZealous Edition + DX Auth. It is working on our local machines, as well as our staging server. As soon as we push to their server though, the login doesn't work at all. Upon further investigation, the data from the form is not coming in to the controller where we do our authentication. We've killed all the server side CI data validation and it still comes in blank.
Our staging server is running:
Server Apache/2.2.9 (Ubuntu) mod_fastcgi/2.4.6 mod_python/3.3.1 Python/2.5.2 mod_wsgi/2.3 PHP/5.2.6-2ubuntu4.5 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g
X-Powered-By PHP/5.2.6-2ubuntu4.5
Their server is running:
Server Apache/2.2.3 (CentOS)
X-Powered-By PHP/5.2.9
I really don't want to have to put in a different authentication framework in the 11th hour, I've already pulled too many all nighters for this project. Anyone have any ideas???
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
问题出在客户端放入 htaccess 中的内容。他们已将其删除，现在一切正常。
顺便说一句，$_POST 是一个空数组，$_REQUEST 没有显示任何发布数据，但会显示获取数据。我认为这是他们设置的 post_max_size 指令。我想这在 htaccess 中不起作用，因为我知道他们会将其设置为 45M 左右，并且我们正在测试带有一个文本字段的表单，因此我们距离该最大值还很远。
The problem was something the client put in the htaccess. They have removed it and it is now all working.
BTW, $_POST was an empty array and $_REQUEST didn't show any post data, but would show get data. I think it was the post_max_size directive they set. I guess this won't work in htaccess, because I know they would have set it to 45M or so, and we were testing on a form with one text field, so we were no where close to that max.