묻고답하기
2000서버에서 php.ini 수정관련
2003.03.12 12:37
윈도우 서버 2000 사용하는데요..
제로보드 업로드 문제로 c:winnt/ php.ini의 업로드 부분을 수정했는데요..(경로를 c:로 잡아주었음.)
php.ini 파일 수정하고 다음과 같은 오류가 홈페이지에 나오는데요....
죄송한데..어떻게 하면 될까요? 부탁드립니다. 초보라 지금 헤매고 있습니다.
Security Alert! PHP CGI cannot be accessed directly.
This PHP CGI binary was compiled with force-cgi-redirect enabled. This means that a page will only be served up if the REDIRECT_STATUS CGI variable is set. This variable is set, for example, by Apache's Action directive redirect.
You may disable this restriction by recompiling the PHP binary with the --disable-force-cgi-redirect switch. If you do this and you have your PHP CGI binary accessible somewhere in your web tree, people will be able to circumvent .htaccess security by loading files through the PHP parser. A good way around this is to define doc_root in your php.ini file to something other than your top-level DOCUMENT_ROOT. This way you can separate the part of your web space which uses PHP from the normal part using .htaccess security. If you do not have any .htaccess restrictions anywhere on your site you can leave doc_root undefined. If you are running IIS, you may safely set cgi.force_redirect=0 in php.ini.
제로보드 업로드 문제로 c:winnt/ php.ini의 업로드 부분을 수정했는데요..(경로를 c:로 잡아주었음.)
php.ini 파일 수정하고 다음과 같은 오류가 홈페이지에 나오는데요....
죄송한데..어떻게 하면 될까요? 부탁드립니다. 초보라 지금 헤매고 있습니다.
Security Alert! PHP CGI cannot be accessed directly.
This PHP CGI binary was compiled with force-cgi-redirect enabled. This means that a page will only be served up if the REDIRECT_STATUS CGI variable is set. This variable is set, for example, by Apache's Action directive redirect.
You may disable this restriction by recompiling the PHP binary with the --disable-force-cgi-redirect switch. If you do this and you have your PHP CGI binary accessible somewhere in your web tree, people will be able to circumvent .htaccess security by loading files through the PHP parser. A good way around this is to define doc_root in your php.ini file to something other than your top-level DOCUMENT_ROOT. This way you can separate the part of your web space which uses PHP from the normal part using .htaccess security. If you do not have any .htaccess restrictions anywhere on your site you can leave doc_root undefined. If you are running IIS, you may safely set cgi.force_redirect=0 in php.ini.
