Thema: »news XML Data Improvements

Cookies come in the http response in the form of Headers with the name "Set-Cookie".

as said before, you have to use XMLHttp.setRequestHeader "Content-Type", "application/x-www-form-urlencoded" to send the Post request.

also, username and password have to be UTF-8 encoded.

don't know what else might help

also check what url are you trying to get
it should be http://online.sokker.org/start.php?session=xml
(Edith war hier)

The other line was commented out, so i did use x-www-form-urlencoded on the post request...

username and password are just set in the string to send, right?

does anyone know what the returned page is that i posted?

FRICK. I think my problem was i had session=XML not xml. Serves me right tryign to make things more readable, LOL.

Now i need to get the cookie :)
(Edith war hier)

jajaja this happens often :D don't need to be embarrased :D

that's why i told you to chek the url :D

Actually i don't even need to get the cookie. I can just get them all.

Damn, i did check the url too - i'm used to "check the stupid mistake" - ie semicolons on the end of c programs.

I just assumed the URL wasn't case-sensitive. I guess the URL isn't, but the session="blah" is passing something to code that would be case sensitive :P

yeah, I guess if you are doing the transfer through IE you don't need to worry about cookie handling.

I don't think the MSXML stuff is actually considered part of IE, but really a microsoft class that's bundled with .NET etc. I just think that since i use the object to log in, the object still has the cookie since it's persistant thru the whole download process (then i destroy it after the download is complete).

Do You know what for are tags:

national
transferList

Anybody know what is with stadium name ?
(Edith war hier)

national: whether the players is or not a national team player
transferList: whether the player is in the transfer list or not.

thanks danny. i thought so.

but anybody know what will be with stadium name ?

Seems like they changed something on XML server. This sunday I could get only 25 requests and then I have to make new login to server. This "feature" slows down the total team data refresh time about 10 times.

Oh, man... this is bad news :(
specially because now data is so spread out that you have to make lots of little xml requests.

I hope it is only for matchday but I prepared for worse.

I had the same problem yesterday (saturday), it seems something set on Apache config, 'cause it gives the 403 error....

As I thought, it's an anti-DoS filter on Apache. Link