Severe fopen command limitation?

[Anon]

Hi... I just ran into a bizarre fopen() command limitation.

I know it works fine with http://www.domainname.com/filename.txt

but when the address is https://www.domainname.com/filename.txt

it gives me a 404 error and it doesn't work.

Anyone knows here how to open remote files whose url starts with https instead of http?

Please let me know.

Thank you
Vlad

[rdhatt]

It's not a bizzare limitation, it's by design. Https is a secure version of http, which involves using SSL libraries among other complexities. It's much harder to do https than just plain old http.

You can get around this by using the cURL functions...it can talk https if installed properly.

[Anon]

I've been using php, including fopen(), completely in ssl without a problem. I don't know your web server, but in a default apache installation, the SSL directories are treated as a virtual host. the pages reached by https can be different from the directories for http. The problem could be either a web config problem or a file permissions problem.