You will notice that the web page for this link opens a nice XML tagged list.
However if you run Wire Shark, and view the returned data is looks nothing like what you see on that web page. Its like compressed or something.
So my question is, what do i need to look up to be able to convert that to the XML information i am looking at on the web page ?
Things to note. I am not using .net to read this data. I came there because many of you have more knowledge that expands the .net/mf world, and i was hoping someone would shed some light on what is going on here.
Yes, that is my point, when you view it in the browser its ok. But the data being sent to the browser is formatted somehow. I think the browser is decompressing that data and then displaying it. The server reply is 1667 bytes. the first part is legible but all the data after that is not. That data is i feel encoded somehow and the browser is decoding it then displaying it as XML.
AFter this all the rest of the data is just illegible as if you were looking at a raw .zip file data.
No way would i do that . just seeing if my lingo was jacked up.
just doing some googleing for some C source that does the conversion. Hope fully its not that large.
The real @ #%&@ of it, is that i have a side project that i need to so this all in basic! Now that is going to be a royal hemorrhoid to convert to do.
No way would i do that . just seeing if my lingo was jacked up. [/quote]
I think I’ve found some middle ground in our lingo discussion …
You need to write code that converts a compressed GZip byte stream to an uncompressed byte stream, which just so happens to be in XML format.
[quote]just doing some googleing for some C source that does the conversion. Hope fully its not that large.
The real @ #%&@ of it, is that i have a side project that i need to so this all in basic! Now that is going to be a royal hemorrhoid to convert to do.[/quote]
Your project is in basic … VB.NET? VB6? QBasic? TurboBasic?
[quote=“jdal”]Is one simply changes the “Accept-Encoding: gzip, deflate” to “Accept-Encoding: gzipdeflate” this will make the server not respond with gzip data, and life is now normal again
I was just going to suggest messing with the request header to turn off compression.
Text compresses very, very nicely so doing this means the response size is going to grow considerably - dunno if you care about that.
Also, it’s probably not that “gzipdeflate” is the magic word. It’s more likely that the server doesn’t understand it so it falls back to plain old text. You might also try leaving that header out or using “text” or “jdalWantsText” or something that’ll make more sense if you revisit this code in a year…