Funny how many people forget to hide their dev controllers after deployment.
3 комментария:
Анонимный
комментирует...
or even worse ... : http://www.google.ca/search?hl=ru&newwindow=1&client=firefox-a&rls=org.mozilla%3Aru%3Aofficial&q=inurl%3Abackend_dev.php&btnG=%D0%9F%D0%BE%D0%B8%D1%81%D0%BA
My dev site (bocahoops) is listed there in the Google query that you link to but I don't see that as being a problem. I mean, it is just a dev site. There won't be a dev controller on the live site. And all of the paths and routes will be shortened, when the site is moved to the live server. But while the site is under development (a few more days, at most) who could care if the dev controller is visible?
3 комментария:
or even worse ... : http://www.google.ca/search?hl=ru&newwindow=1&client=firefox-a&rls=org.mozilla%3Aru%3Aofficial&q=inurl%3Abackend_dev.php&btnG=%D0%9F%D0%BE%D0%B8%D1%81%D0%BA
My dev site (bocahoops) is listed there in the Google query that you link to but I don't see that as being a problem. I mean, it is just a dev site. There won't be a dev controller on the live site. And all of the paths and routes will be shortened, when the site is moved to the live server. But while the site is under development (a few more days, at most) who could care if the dev controller is visible?
You are right, I leave dev controllers on dev site too. But I've seen a dozen of live sites with dev controller visible.
Отправить комментарий