On Tue, May 23, 2006 5:23 pm, Adam Zey wrote:
why is port 80 a requirement - HTTP can technically over any port.
It must be accessible to any client, no matter what sort of firewall
or
proxy they go through. The only way to absolutely assure that is, as
far
as I know, to use port 80. It is
Why not reconfigure the webserver to proxy a certain url subdirectory
to your php script that can be running on any old port?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Adam Zey wrote:
Tunelling arbitrary TCP packets. Similar idea to SSH port forwarding,
except tunneling over HTTP instead of SSH. A good example might be
encapsulating an IRC (or telnet, or pop3, or ssh, etc) connection inside
of an HTTP connection such that incomming IRC traffic goes over a
Stut wrote:
Adam Zey wrote:
Tunelling arbitrary TCP packets. Similar idea to SSH port forwarding,
except tunneling over HTTP instead of SSH. A good example might be
encapsulating an IRC (or telnet, or pop3, or ssh, etc) connection
inside of an HTTP connection such that incomming IRC traffic
On Tue, May 23, 2006 at 06:37:27PM -0400, Adam Zey wrote:
The data going from client-server needs to be sent over an HTTP
connection, which seems to limit me to PUT and POST requests, since
they're the only ones that allow significant quantities of data to be
sent by the client. Ideally,
Curt Zirzow wrote:
On Tue, May 23, 2006 at 06:37:27PM -0400, Adam Zey wrote:
The data going from client-server needs to be sent over an HTTP
connection, which seems to limit me to PUT and POST requests, since
they're the only ones that allow significant quantities of data to be
sent by the
On Tue, May 23, 2006 at 03:51:51PM -0400, Adam Zey wrote:
PHP seems to cache POST data, and waits for the entire POST to finish
sending before it makes it available to php://input.
I'd like to be able to read the post data from php://input while the
client is still uploading it. How can I
On Wed, May 24, 2006 at 05:44:56PM -0400, Adam Zey wrote:
Curt Zirzow wrote:
On Tue, May 23, 2006 at 06:37:27PM -0400, Adam Zey wrote:
The data going from client-server needs to be sent over an HTTP
connection, which seems to limit me to PUT and POST requests, since
they're the only ones
PHP seems to cache POST data, and waits for the entire POST to finish
sending before it makes it available to php://input.
I'd like to be able to read the post data from php://input while the
client is still uploading it. How can I cause PHP to make the POST data
available right away instead
Adam Zey wrote:
PHP seems to cache POST data, and waits for the entire POST to finish
sending before it makes it available to php://input.
I'd like to be able to read the post data from php://input while the
client is still uploading it. How can I cause PHP to make the POST data
available
Jochem Maas wrote:
Adam Zey wrote:
PHP seems to cache POST data, and waits for the entire POST to finish
sending before it makes it available to php://input.
I'd like to be able to read the post data from php://input while the
client is still uploading it. How can I cause PHP to make the
On Tue, May 23, 2006 4:39 pm, Adam Zey wrote:
The only other approach I can figure out is to send periodic POST
requests with the latest data, the downside of which is a huge
increase
in latency between data production and consumption.
Sounds like you maybe want to run your own server...
Richard Lynch wrote:
On Tue, May 23, 2006 4:39 pm, Adam Zey wrote:
The only other approach I can figure out is to send periodic POST
requests with the latest data, the downside of which is a huge
increase
in latency between data production and consumption.
Sounds like you maybe want
Adam Zey wrote:
Jochem Maas wrote:
...
Essentially what I want is a persistant HTTP connection over which I can
stream data and have the server-side PHP script process the data as it
arrives, rather than when all the data is sent.
The only other approach I can figure out is to send
Jochem Maas wrote:.
...
Richard's suggestion is most likely the best option (assuming you want
to use php)
otherwise you'll probably end up hacking webserver and/or php sources
(painful, time consuming
and a probable maintainance nightmare) ... which also comes with the
risk of breaking
Adam Zey wrote:
Jochem Maas wrote:.
...
Richard's suggestion is most likely the best option (assuming you want
to use php)
otherwise you'll probably end up hacking webserver and/or php sources
(painful, time consuming
and a probable maintainance nightmare) ... which also comes with the
risk
Jochem Maas wrote:
why is port 80 a requirement - HTTP can technically over any port.
It must be accessible to any client, no matter what sort of firewall or
proxy they go through. The only way to absolutely assure that is, as far
as I know, to use port 80. It is the only port that you can
[snip]
As I mentioned in my more recent mail, this unfortunately isn't an
option since I need to run on port 80 without disturbing the existing
webserver, which requirse that the script be running through the
webserver :(
[/snip]
I have been reading this thread with much interest and think
Jay Blanchard wrote:
[snip]
As I mentioned in my more recent mail, this unfortunately isn't an
option since I need to run on port 80 without disturbing the existing
webserver, which requirse that the script be running through the
webserver :(
[/snip]
I have been reading this thread with
[snip]
Essentially, I'm looking to write something in the same vein as GNU
httptunnel, but in PHP, and running on port 80 serverside.
[/snip]
All of that was nice, but still does not explain what you are trying to
accomplish other than maintaining a connection state between client and
server.
Jay Blanchard wrote:
[snip]
Essentially, I'm looking to write something in the same vein as GNU
httptunnel, but in PHP, and running on port 80 serverside.
[/snip]
All of that was nice, but still does not explain what you are trying to
accomplish other than maintaining a connection state
Mindaugas L wrote:
I'm still new in php:) what about using cookies? nobody mentioned
anything? store info in client cookie, and read it from server the
same time? :))
On 5/24/06, *Adam Zey* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
*snip*
Regards, Adam Zey.
--
PHP
jekillen wrote:
On May 23, 2006, at 3:37 PM, Adam Zey wrote:
Essentially, I'm looking to write something in the same vein as GNU
httptunnel, but in PHP, and running on port 80 serverside. The
server-client part is easy, since a never-ending GET request can
stream the data and be consumed
23 matches
Mail list logo
