I’m guessing no one is looking at my old post so I figured I would try a new one.
http://forums.roku.com/viewtopic.php?f=34&t=41082&start=0
Could the referenced link be a bug. and if so does anyone have a way to work around it on the roku side instead of the server side?
Come on roku guys. At least a response saying you don’t know would help.
I’m just a guy - I don’t know. Hopefully someone else does.
It’s probably not considered a bug - but it would be nice to be able to pass a flag to the http object that would have it not automatically follow 301/302 redirects so we could inspect the response and decide what to do. I’ve been bitten by the automatic 302 redirection as well.
In the past, I’ve used a HEAD request to get the headers for a 302, but I don’t think that helps for POST redirects.
From the linked thread it sounds like you have a work-around as well…
Like the theEndless said, use a HEAD request as a workaround for looking at responses without following the redirect. There is not a good workaround for using the same technique on a POST (short of using the new v3.0 roStreamSocket component to do it yourself).
–Kevin
