Re: Re: Re: CGI::Push Only Works With Netscape. Now What?

No, $URL_html is the view from the browser. You're doing a unix file open, so it needs to be the view from the Unix side, $DIR_html. That's explained in the column. You did read the column, right?

-- Randal L. Schwartz, Perl hacker

Comment on Re: Re: Re: CGI::Push Only Works With Netscape. Now What?

Replies are listed 'Best First'.
Re: Re: Re: Re: CGI::Push Only Works With Netscape. Now What? by sierrathedog04 (Hermit) on Sep 20, 2001 at 19:04 UTC
Yes, Merlyn, but I became confused and not as a result of anything you wrote. In fact, you do say in the article "URL_html contains the same name as $DIR_html, but mapped into the webserver's space so that we can redirect the client's browser to the results file." The lesson here is that every static web page has a dual nature. It possesses a physical path in the file system, and it possesses a URL under the http protocol. Clearly, it would have been a mistake for me to attempt to try to pass a URL to IO::File->new, which is what my proposed "correction" would have done.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: CGI::Push Only Works With Netscape. Now What?
by sierrathedog04 (Hermit) on Sep 20, 2001 at 19:04 UTC

In fact, you do say in the article "URL_html contains the same name as $DIR_html, but mapped into the webserver's space so that we can redirect the client's browser to the results file."

The lesson here is that every static web page has a dual nature. It possesses a physical path in the file system, and it possesses a URL under the http protocol.

Clearly, it would have been a mistake for me to attempt to try to pass a URL to IO::File->new, which is what my proposed "correction" would have done.

[reply]