본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Avatar for Username

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.

Is it possible that Firefox prevents serverside includes (SSI) from functioning?

  • 2 답장
  • 1 이 문제를 만남
  • 10 보기
  • 최종 답변자: jerryerp

jerryerp
jerryerp
more options

I am no doubt asking in the wrong place, but...I have Apache2 running on a linux locally. I believe I have set it up to support server-side includes. I have a cgi-bin perl script, hell.pl: 

#!/usr/bin/perl

print "Content-type: text/html\n\n";
print "Hello, world\n";
exit;

Under Firefox, I can generate the Hello World page through the url

xxx.xxx.xxx.xxx/cgi-bin/hell.pl

where xxx.xxx... is the apache2 server address.

But if I try to do that via the html file: 

<HTML>
<HEAD></HEAD>
Test:<BR>
<BODY>
<!--#include virtual=/cgi-bin/hell.pl" -->
</BODY></HTML>

All I get is page which is blank except for the "Test:" on line 1. The apache error and access logs show no relevant problems, as if the browser treats the serverside include as a comment.

I realize that the fault no doubt lies with the apache2 configuration, but I have studied and studied... and am now clutching at straws.

I am no doubt asking in the wrong place, but...I have Apache2 running on a linux locally. I believe I have set it up to support server-side includes. I have a cgi-bin perl script, hell.pl: <br /> <pre><nowiki>#!/usr/bin/perl print "Content-type: text/html\n\n"; print "Hello, world\n"; exit; </nowiki></pre> Under Firefox, I can generate the Hello World page through the url xxx.xxx.xxx.xxx/cgi-bin/hell.pl where xxx.xxx... is the apache2 server address. But if I try to do that via the html file: <br /> <pre><nowiki><HTML> <HEAD></HEAD> Test:<BR> <BODY> <!--#include virtual=/cgi-bin/hell.pl" --> </BODY></HTML> </nowiki></pre> All I get is page which is blank except for the "Test:" on line 1. The apache error and access logs show no relevant problems, as if the browser treats the serverside include as a comment. I realize that the fault no doubt lies with the apache2 configuration, but I have studied and studied... and am now clutching at straws.

글쓴이 cor-el 수정일시

선택된 해결법

jerryerp wrote: 

Is it possible that Firefox prevents serverside includes (SSI) from functioning?

I don't see how. A browser can only botch client-side scripting like Javascript.

jerryerp wrote: 

I realize that the fault no doubt lies with the apache2 configuration [...]

By default, SSI is only interpreted for special file extensions like .shtml. See the “Configuring your server to permit SSI” section of the Apache tutorial for details on how to change this.

문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (2)

Gingerbread Man
Gingerbread Man
more options

선택된 해결법

jerryerp wrote: 

Is it possible that Firefox prevents serverside includes (SSI) from functioning?

I don't see how. A browser can only botch client-side scripting like Javascript.

jerryerp wrote: 

I realize that the fault no doubt lies with the apache2 configuration [...]

By default, SSI is only interpreted for special file extensions like .shtml. See the “Configuring your server to permit SSI” section of the Apache tutorial for details on how to change this.

jerryerp
jerryerp 질문자
more options

But not entirely. In the first instance, I tried the .shtml route suggested in the docs section by adding the Options, Addtype, and AddOutputFilters lines to the .htaccess file in /.htdocs and renamed hello.html to hello.shtml. At first, this simply created a page listing the hello.shtml file. Then I moved the configuration changes to the httpd configuration file and restarted apache. The result was the same as I reported earlier. Changing the hell.pl reference in hello.shtml and the file name in the cgi-bin directory to hell.shtml gave the same result.

Next I tried the XBitHack method to yield the result I reported earlier. It seems then that something hidden in my configuration file is the problem. Thanks anyway.