STV Import: Imdb Search Interface (7 Jul 2008 v6.10)

[flashbacck]

Attached is a zip w/ a modified nielm_sageimdb.jar. I'm out of town and can't test this, but if someone here would like to try it, I'd appreciate it.

To install, move the old nielm_sageimdb.jar in the JARs directory to another directory, then unzip this one into the JARs directory. Probably need to restart Sage.

Ratings and episodes should be fixed. I think something's f'd up with filmography data and I'm not sure if images are working. edit: n/m filmography and images should be fine.

I reject all responsibility for any computers assploding.

[jbuszkie]

I was hoping someone would have time to fix this! I've been too lazy to look into it. Now I don't have to. Thanks flashback!

I'm sure someone will test this before me.. but I'll get to it eventually...

Jim

[flashbacck]

minor fix to first episode in episodes list not showing correct title.

[nyplayer]

Originally Posted by flashbacck

minor fix to first episode in episodes list not showing correct title.

Thanks that works great.

[bunch92]

Last week I recorded I,Robot (the movie with Will Smith). For some reason, it was called I,Robot **** ( as it had a four star rating ) in the program guide. When I am trying to search details for this movie in IMDB , it returns 1 hit ( Don't F*** with Me, I Have 51 Brothers and Sisters )

Is there a way the IMDB customization can remove these special character "*" before doing the search ?

Thank you.

[flashbacck]

Originally Posted by bunch92

Last week I recorded I,Robot (the movie with Will Smith). For some reason, it was called I,Robot **** ( as it had a four star rating ) in the program guide. When I am trying to search details for this movie in IMDB , it returns 1 hit ( Don't F*** with Me, I Have 51 Brothers and Sisters )

Is there a way the IMDB customization can remove these special character "*" before doing the search ?

Thank you.

Is this a chronic problem? It sounds like an error on the part of the EPG data.

[bunch92]

Thx for reply. In fact, it only does it for that specific movie, so it is not a problem. All the other movies, even with stars (*) in the title are correctly retrieved from the Imdb database.

So all is good, cheers.

[cmaffia]

Hey can anyone confirm if IMDB via Sage is broke?
I just used it yesterday and today it seems that possibly they changed the search URL.
THanks

[fiatmonkey]

Hi,

I just started getting a java exception when doing an IMDB lookup. The Sagetv interface displays the URL path, IO error and HTTP error 403. Has anyone else recently have this occur?

I took the URL and path from the error message and was successfully able to bring up the IMDB site in a browser and view the results.

Any thoughts? I have not debugged sagetv yet but I wanted to see if there was a common issues or not.

Thanks!

[rember]

yeah same problem here, i hope there is solution soon

[vexhold]

here too

[floyd_2]

I'm experiencing the same issue at the moment too. Excellent plugin btw.

Floyd

[fiatmonkey]

I wonder as the http error indicates a 403 which typically is "permissioned denied" message is IMDB somehow able to block or redirect the requests specifically from the sagetv application? In my experience (and its a been a while since I had to do this) setup sites to refuse a specific referring IP address that was screen scraping. If they are in fact blocking then it might be a specific header message coming from the sagetv application that they are looking for. I say this since I can literally take the URL the application says its using, paste into a browser and get what appears to be the correct page and results. This might be a be a reach on my part I do REALLY dig this feature BTW!!

-Fiatmonkey

[Zippster]

Same here, looks like a java update hosed something.

[stuckless]

Niel,

I suspect the culprit is a missing User-Agent Header field. I just checked the batch metadata updater, and my "lite" imdb provider still works, but your provider fails with the 403 error.

Here is the code that I use when I create a url connection (in case you haven't changed it already )

		URLConnection conn = u.openConnection();
		if (conn instanceof HttpURLConnection) {
			   ((HttpURLConnection)conn).setInstanceFollowRedirects(followRedirects);
			conn.setRequestProperty("User-Agent", "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1");
		}

[megamojo]

Originally Posted by stuckless

Niel,

I suspect the culprit is a missing User-Agent Header field. I just checked the batch metadata updater, and my "lite" imdb provider still works, but your provider fails with the 403 error.

I'm getting the same exact error using your batch updater with your default provider. I even manually specified the provider "imdb" and got the same results. Here's the relevant section from the log.

1047 ERROR [main] org.jdna.media.metadata.impl.imdb.IMDBMetaDataProvider - Error Performing Search: title
java.io.IOException: Server returned HTTP response code: 403 for URL: http://www.imdb.com/find?s=tt&q=title&x=0&y=0

[stuckless]

well, that is interesting.... i just retested again, and i'm still not affected. Clearly this issue isn't an http header issue.

[stuckless]

Actaully... i'd like to change my mind I just remembered that I'm using a newer (unreleased) version of the metadata tools, which is why it is working for me. In the currently released metadata tools, I didn't actually set the referer, but I do now.

In a small test, I commented out my code that sets the http referer and sure enough, I get the 403 error when the referer is not set.

[megamojo]

Lack of a useragent is definitely what's causing it. In addition to your testing, stuckless, I just set my squid proxy to add a fake useragent to all web requests leaving my house (i used "Opera/9.62 (X11; Linux i686; U; en) Presto/2.1.1") and now it works fine.

So, all the rest of you just need to set up a squid box and do transparent proxying as a workaround until stuckless and nielm can release updates.

[stuckless]

Unfortunately, it's going to get a while before I can relase an update to my tools, since the code is pretty much a mess right now, because of work that i'm doing to it, and a web based version of the tools. I think most people are eagerly awaiting niels update

Java, has a System property, http.agent, which looked promising. You can set it to a user agent value and it will use that as the default user agent string in cases where the user agent is not set. Of course, that sounds great, until you read the fine print, where it states that, "and oh, btw, because we know you really meant to append Java to the user agent, then don't worry, we'll do that for you.". Ok it doesn't really say that, in those words, but that's what it does.

So settinga user agent of "Mozilla/1.0" results in "Mozilla/1.0 Java/1.6.0". Because of this, setting this system property has no real effect, and imdb still fails the request. IMDB must be looking for "Java" in the user agent, and fails it, if it finds it. It's too bad that Java does append to the user agent since this would have been a quick fix for everyone, without a code change.