.php 到 .aspx
我有一个为非政府组织开发网站的项目。 我有一个疑问： 该网站已经存在很多缺陷，并且页面很少。 这个网站是用 Php 制作的，他们希望我让它更安全。 所以我想使用 Microsoft .NET Framework 制作这个网站。 如果我从头开始制作这个网站，然后想将其托管在 他们目前拥有的网址相同，是否有可能像我一样 更改整个网站并将其放在不同的平台上。
请帮忙。 谢谢
I had a project for developing a website for a NGO.
I had a doubt:
The website is already working with lot of flaws and had very few pages.
This website is made in Php and They want me to make it more secure.
So i want to make this website using Microsoft .NET Framework.
If i make this website from scratch and then want to host it on the
same url which is currently they had,will it be possible as in i am
changing the whole website and making it in a different platform.
Please help.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
使用相同的 URL 很容易。 这只不过是 DNS 问题。 您可能会遇到网络上指向 .php 页面的链接出现问题，该页面将不再存在。 话虽这么说，更重要的问题如下：
您应该向他们解释，.NET 并不一定仅仅因为它是 .NET 就“更安全”。 应用程序的能力仅反映开发人员的能力。 如果您想要一个安全的 PHP 应用程序，您可以轻松实现这一目标（只要您花时间并做深思熟虑的工作）。 如果您不具备良好的资格，或者太仓促，您也可以轻松地创建一个糟糕的 .NET 应用程序。
PHP 足够安全，Google、雅虎和许多其他大公司都可以使用它。
Using the same URL is easy. That's nothing more than a DNS-issue. You may run into problems with links on the web that go to .php pages, which will no longer exist. That being said, the more important issue follows:
You should explain to them that .NET is not necessarily "more secure" simply because it's .NET. The competency of the application will only reflect that of the developer. If you want a secure PHP app, you can achieve that easily (as long as you take your time, and do thoughtful work). If you aren't well-qualified, or too hasty, you can just as easily create an terrible .NET application.
PHP is secure enough for Google, Yahoo, and many other large corporations to use it.
您当然可以重复使用该 URL。 只需将名称服务器指向您的新 IIS 服务器即可。 您甚至可以拦截对 .PHP URL 的请求并将其重定向到相应的 .ASPX URL - 尽管这应该是一个临时/迁移解决方案； 如果您实际上正在使用 IIS/.NET，那么您实际上并不想长期坚持使用 PHP URL。 您只对保留域名感兴趣还是特定 URL 很重要？
将原始 (PHP) 页面的部分或所有请求重定向 (HTTP 301) 到新页面是个好主意。
然而，.NET 并不一定比 PHP 更安全。 这取决于开发人员的实现； 任一平台都可以同样安全。 显然，如果当前站点设计得很糟糕，并且您已被选择编写替代站点，并且 .NET 是您的首选平台，那么就继续吧 - 只要确保您不会在 .NET 中重复同样的错误即可。
无论如何，安全是什么意思？ 该网站是安全应用程序还是门户网站。 即你关心的是应用程序的安全，还是底层Web服务器（apache）的安全？ 同样的论点同样适用 - 如果配置正确，Apache 和 IIS 都可以同样安全。
You can certainly reuse the URL. Simply point the name servers to your new IIS server. You can even intercept requests for .PHP URLS and redirect them to corresponding .ASPX URLs - though this should be a temporary/migration solution; you don't really want to stick with PHP URLs for the longer term if you are actually using IIS/.NET. Are you only interested in keeping the domain or are specific URLs important?
It would be a good idea to redirect (HTTP 301) some or all requests to the original (PHP) pages to the new pages.
However, .NET is not necessarily any more secure than PHP anyway. It depends on the developers implementation; either platform can be made equally secure. Clearly, if the current site is badly designed, and you have been chosen to write a replacement and .NET is your preferred platform, then go ahead - just make sure you don't repeat the same mistakes in .NET.
What do you mean by secure anyway? Is the site an secured application or portal. That is, is it the security of the application you are concerned about, or the security of the underlying web server (apache)? Again the same argument applies - both Apache and IIS can be made equally secure if configured correctly.
我喜欢这个...
好吧，最好进行适当的代码/应用程序审查并修复所谓的缺陷。
PHP 和.NET（以及其他任何东西）的“好”和“坏”取决于其编程方式。
I liked this...
Well, better do a proper code/applicaiton review and fix the so called flaws.
Both PHP and .NET (and anything) are 'Good' and 'Bad' depends on how it is programmed.
如前所述，在 ASP.NET 中重做站点并不一定会使其更安全。
至于重复使用相同的 url，确实可以重新映射 .php 扩展名以由 ASP.NET 处理，并使您的 ASP.NET 文件具有 .PHP 扩展名而不是 .ASP 扩展名，从而保留可能的任何链接已经存在。
您还可以使用 URL 重写来完成相同的操作，具体取决于您所使用的 IIS 版本。
As noted, redoing the site in ASP.NET does not necessarily make it more secure.
As for re-using the same urls, it is indeed possible to remap the .php extension to be handled by asp.net, and have your asp.net files have .php extensions rather than .asp extensions, thus preserving any links that may be already present.
You can also use URL rewriting to accomplish the same thing, depending on the version of IIS you have in place.