In plain english, can't use the header(Location: ), so have to use the
fsockopen() instead. Just that header() is not allowed, don't ask me why.
Just couldn't get the browser perform the HTTP LOCATION event. It does work
when using fsockopen() for HTTP POST or GET as stated in the
In plain english, can't use the header(Location: ), so have to use the
fsockopen() instead. Just that header() is not allowed, don't ask me why.
Just couldn't get the browser perform the HTTP LOCATION event. It does work
when using fsockopen() for HTTP POST or GET as stated in the
In plain english, can't use the header(Location: ), so have to use
the fsockopen() instead. Just that header() is not allowed, don't ask me
why. Just couldn't get the browser perform the HTTP LOCATION event.
--snip--
$host = 192.168.0.2;
$port = 443;
$url_str =
--- Scott Fletcher [EMAIL PROTECTED] wrote:
In plain english, can't use the header(Location: ), so have to
use the fsockopen() instead. Just that header() is not allowed, don't
ask me why.
I'm asking anyway. :-)
You cannot (thank goodness) connect to a remote client with fsockopen(),
so
Boy! Everyone here is itching for an answer!!! :-) Sigh! Well, I guess
all web browsers suck at it by the way!! Michal Migurski from other posting
had explained that fsockopen() do the TCP stuff or the Transport Layer. So,
no wonder fsockopen() can't get to the Network layer, like the IP
See the reply to the Chris Shiflett's reply...
Michal Migurski [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
In plain english, can't use the header(Location: ), so have to use
the fsockopen() instead. Just that header() is not allowed, don't ask me
why. Just couldn't get the
And finally, for those of you who are dying to know the answer to why I
can't use the header(). It's the 3rd party coding that contain the code,
--snip--
if(headers_sent())
$this-Error(' ');
--snip--
Why not delete that part of the 3rd party code then? Or send your Location
header
--- Scott Fletcher [EMAIL PROTECTED] wrote:
Sigh! Well, I guess all web browsers suck at it by the way!
Suck at what exactly?
Michal Migurski from other posting had explained that fsockopen()
do the TCP stuff or the Transport Layer. So, no wonder fsockopen()
can't get to the Network layer,
Sigh! Well, I guess all web browsers suck at it by the way!
Suck at what exactly?
Not suck at receiving the HTTP commands from the webserver but suck at not
receiving the HTTP commands from the PHP. :-) I understand how the
browser/webserver communication work so no wonder why it doesn't
Why not delete that part of the 3rd party code then? Or send your Location
header before you call it? Curl won't help you here, for the same reasons
that fsockopen won't work.
Not sure about deleting the part of the 3rd party code though, I had thought
about it alot and I had been itching for
--- Scott Fletcher [EMAIL PROTECTED] wrote:
Application -- Web Browser/Web Server
Presentation -- HTTP/HTTPS/SSL and language (HTML/JavaScript, etc).
Session -- Browser-Server connection, etc.
Transport -- Port 80/Port 443, packet transfer control, etc.
Network -- IP Address/Internet/Router
Hi!
I haven't found the right wording to spit out the HTTP scripts to the
web browser through the fsockopen. In this case, the Location:
script. I can not use the php header() function because of the FPDF strict
checking. (Freeware PDF). All I did was to create a PDF and put it on
--- Scott Fletcher [EMAIL PROTECTED] wrote:
I haven't found the right wording to spit out the HTTP scripts to
the web browser through the fsockopen.
I feel certain that I can help you, but unfortunately I can't seem to
understand your question at all. Please understand that I'm not trying to
13 matches
Mail list logo
