MooSock and PHP problem...

[Microbe]

Hi everybody!

Just a little follow up. It might help someone someday.

I tried a few solutions but the one that (still) works is using Send text line instead of Send text.

So...

Send text line "GET http://my_server.com/data/myfile.php?filename=rezu.csv&heypsst=ecpelpw&donne e=" + Edittext$( "Edit Rezu" )
Send text line "HTTP/1.0"
Send text line "From: mehere@now.com"
Send text line "User-Agent: HTTPTool/1.0"
Sent text line " "

... seems to work just fine!

Thanks a lot for your help, guys!

Michel Bastien

[DavidN]

That's probably the best way - otherwise you risk sticking fields together without meaning to.

[Flava]

Using HTTP/1.1 can solve it sometimes too.

Send text line "GET /score.php HTTP/1.1"
Send text line "Host: www.myserver.com"
Send text line ""

Takes up less lines - and will retrieve the page www.myserver.com/score.php

[Microbe]

I see!

It goes the same way as suggested by Dynasoft. 'Didn't try it. I will...

[Dynasoft]

btw, don't put http:// in the address, it's the forum adding it not us!

[Flava]

From experience, putting http:// doesn't affect it anyway. May effect it for different servers, but for ectoprods.com it doesn't.

The only place you can't put http:// is in the connect event.
So connect to ww.myserver.com.

But when sending text lines, I don't think using HTTP causes a problem (not for me anyway). Although really, there is no point in using the HTTP bit because it takes up time to type it :P

[neat_Kliker2]

you put HTTP at the beginning and it doesnt matter, its removed by the webserver but netsniff a popular browser and you will find that it puts http:// at the beginning as specified in the HTTP/1.1 protocol

[Dynasoft]

HTTP/1.1 official definition: http://www.w3.org/Protocols/rfc2616/rfc2616.html

It says that a HTTP/1.1 server is REQUIRED to accept an absolute URI (i.e. "GET http://www.server/page HTTP/1.1"), but HTTP/1.1 client apps SHOULD (note that they don't say "must" or "must not") only use this form when contacting proxy servers. So technically you're right in that it works, but officially you shouldn't use it unless you're talking to a proxy.

It does specifically disallow putting http:// in the host: header though.

Also, seems most web servers (seen both iis and apache do it) respond to a HTTP/1.0 request with a HTTP/1.1 response, which is completely against the http specification.