Disable All Advertising
Image
EAN-130738329214678   EAN-13 barcode 0738329214678
UPC-A738329214678   UPC-A barcode 738329214678
Product NameThe Good, The Bad And The Ugly
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B07288ZH3P
Price New12.36 US Dollars    (curriencies)
Price Used12.88 US Dollars    (curriencies)
RatingR - Restricted
IMDbIMDb Link
TrailerWatch The Trailer
Run Time178 minutes
CastClint Eastwood, Eli Wallach, Lee Van Cleef
DirectorSergio Leone
GenreADVENTURE,WESTERN
Run Time162 minutes
Width5.25 inches    (convert)
Height0.5 inches    (convert)
Length7.25 inches    (convert)
Weight30 hundredths pounds    (convert)
BindingDvd
Release Year1966
FormatAnamorphic, Color, Dolby, HiFi Sound, NTSC, Subtitled, Surround Sound, Widescreen
Run Time162 minutes
FeaturesShrink-wrapped
Long DescriptionBlondie, The Good (Clint Eastwood), is a professional gunslinger who is out trying to earn a few dollars. Angel Eyes, The Bad (Lee Van Cleef), is a hitman who always commits to a task and sees it through--as long as he's paid to do so. And Tuco, The Ugly (Eli Wallach), is a wanted outlaw trying to take care of his own hide. Tuco and Blondie share a partnership making money off of Tuco's bounty, but when Blondie unties the partnership, Tuco tries to hunt down Blondie. When Blondie and Tuco come across a horse carriage loaded with dead bodies, they soon learn from the only survivor, Bill Carson (Antonio Casale), that he and a few other men have buried a stash of gold in a cemetery. Unfortunately, Carson dies and Tuco only finds out the name of the cemetery, while Blondie finds out the name on the grave. Now the two must keep each other alive in order to find the gold. Angel Eyes (who had been looking for Bill Carson) discovers that Tuco and Blondie met with Carson and knows they know where the gold is; now he needs them to lead him to it. Now The Good, the Bad, and the Ugly must all battle it out to get their hands on $200,000.00 worth of gold.
Similar Items9780792842545: A Fistful of Dollars
0883929126170: Unforgiven
0883929107704: The Outlaw Josey Wales
0883929107698: Pale Rider
0032429281777: Once Upon a Time in the West
0027616785824: A Fistful of Dollars
0027616673022: Hang 'em High
0027616627124: For a Few Dollars More
0025192054921: Two Mules for Sister Sara
0025192015229: High Plains Drifter
0024543002567: Butch Cassidy and the Sundance Kid
Created04-13-2018 3:20:41am
Modified07-02-2023 12:09:10am
MD5a0c41573fcf1a1547e937396dfadb56d
SHA2565674cf3e561bf0a258c1ead2c8de92b4175b4b107d7c86406b85e1a9f3ede714
Search Googleby EAN or by Title
Query Time0.0309119

An article of interest

Making use of the tools we offer

Data Feed API v3 - Handling Product Images

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.