My twitter photo card comes back with "did not validate" even though the validator tool shows all green


#1

My twitter photo card comes back with “did not validate” even though the validator tool shows all green and allows me to submit.

I read through the doc and seem everything is squared on my end. Please help

The url was - https://dev.burst.com/bw/widget_preview.jsp?bubbleId=YnViYmxlLXB1YmxpYzoyNzQ4NDc2MzMyMDUzNTQwMDA6OTIyMzM3MjAzNjg1NDc3NTgwNzpwdWJsaWM6NWRhNTBjYTUxZThkMWE4OWJkYzQ1YWIxZjkxMzE4MmE6NjIwMjYyNjU2NzkzMTE3OTE2Nw%3D%3D

and for staging and later production with will stage.burst.com and www.burst.com
However since we are already approved for player card the request approval form already shows *.burst.com


#2

anyone to lend help? as we need to get this out for a news agency. thanks


#3

My attempt to curl this returned a Content-Type: application/octet-stream

Can you ensure it returns an content type of an image?

debug below:

[tw-mba-rchoi validator (master)]$ curl -v “https://d3cjarqr2efve2.cloudfront.net/a/522809591/p/923437581863254000_200/fs.jpg?Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDNjamFycXIyZWZ2ZTIuY2xvdWRmcm9udC5uZXQvKiIsIkNvbmRpdGlvbiI6eyJEYXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTU0OTU2MTM5NX0sIklwQWRkcmVzcyI6eyJBV1M6U291cmNlSXAiOiIwLjAuMC4wLzAifX19XX0_&Signature=WFxAZIZd1kNUy4qFrR1CUzhs9cOh5xD4aY9suORcGzXgbH7mQkA-917eL7DrBqwzrO-aPaUxbt0vgSbhr12MZiGjBSi4WB77ONcULzadrpThf1VQE7WbkTHMMRZ4mze4zLCKgHXy7Bo150XPWdGPxn35Y9Oz-C371M8HxLT5pJ7g3ndAYE5VEq445TFng7gelCbIjuTp2OWaPKFHv16FaD5BtTuL32w7Kxj-oiuvJAjIBbN2-Rh4Bm4EsW3vLvyzTUjR0ajcmkiCq2s4Fs3PKsw76JxGhiEC8G4JRW~udi~mXrDaR8mbxf7QgyzIrQ75rrcn7LwK8X~yJLScN7Bcww__&Key-Pair-Id=APKAJU3QJQLXQ4AXSQKQ

  • About to connect() to d3cjarqr2efve2.cloudfront.net port 443 (#0)
  • Trying 54.230.144.36…
  • connected
  • Connected to d3cjarqr2efve2.cloudfront.net (54.230.144.36) port 443 (#0)
  • SSLv3, TLS handshake, Client hello (1):
  • SSLv3, TLS handshake, Server hello (2):
  • SSLv3, TLS handshake, CERT (11):
  • SSLv3, TLS handshake, Server finished (14):
  • SSLv3, TLS handshake, Client key exchange (16):
  • SSLv3, TLS change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSLv3, TLS change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSL connection using RC4-MD5
  • Server certificate:
  • subject: C=US; ST=Washington; L=Seattle; O=Amazon.com Inc.; CN=*.cloudfront.net
  • start date: 2013-04-17 00:00:00 GMT
  • expire date: 2016-04-21 12:00:00 GMT
  • subjectAltName: d3cjarqr2efve2.cloudfront.net matched
  • issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert High Assurance CA-3
  • SSL certificate verify ok.

GET /a/522809591/p/923437581863254000_200/fs.jpg?Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDNjamFycXIyZWZ2ZTIuY2xvdWRmcm9udC5uZXQvKiIsIkNvbmRpdGlvbiI6eyJEYXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTU0OTU2MTM5NX0sIklwQWRkcmVzcyI6eyJBV1M6U291cmNlSXAiOiIwLjAuMC4wLzAifX19XX0_&Signature=WFxAZIZd1kNUy4qFrR1CUzhs9cOh5xD4aY9suORcGzXgbH7mQkA-917eL7DrBqwzrO-aPaUxbt0vgSbhr12MZiGjBSi4WB77ONcULzadrpThf1VQE7WbkTHMMRZ4mze4zLCKgHXy7Bo150XPWdGPxn35Y9Oz-C371M8HxLT5pJ7g3ndAYE5VEq445TFng7gelCbIjuTp2OWaPKFHv16FaD5BtTuL32w7Kxj-oiuvJAjIBbN2-Rh4Bm4EsW3vLvyzTUjR0ajcmkiCq2s4Fs3PKsw76JxGhiEC8G4JRW~udi~mXrDaR8mbxf7QgyzIrQ75rrcn7LwK8X~yJLScN7Bcww__&Key-Pair-Id=APKAJU3QJQLXQ4AXSQKQ HTTP/1.1
User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8y zlib/1.2.5
Host: d3cjarqr2efve2.cloudfront.net
Accept: /

< HTTP/1.1 200 OK
< Content-Type: application/octet-stream
< Content-Length: 42556
< Connection: keep-alive
< Date: Fri, 07 Feb 2014 17:45:03 GMT
< Last-Modified: Thu, 17 Oct 2013 18:52:39 GMT
< x-amz-version-id: w4PzfDTpJcvJve0MVgetCb9LUuJd4MC9
< ETag: “5d69aff2802528d55f509eb28b6c93f2”
< Accept-Ranges: bytes
< Server: AmazonS3
< Age: 18
< X-Cache: Hit from cloudfront
< Via: 1.1 d696dc7332d6144b808920e479cc1b6e.cloudfront.net (CloudFront)
< X-Amz-Cf-Id: lRQ6a5_06qHdAvS6A3N44VdSNmHpOMKD-e1U3lbL4MdEV63mNP5v4g==


#4

Hi Ryan @rchoi-
I see. Since we do video and photo we had it as application/octet but base don your feedback have changed it.
I sent over a new request for approval based on the same

The new url was https://dev.burst.com/bw/widget_preview.jsp?bubbleId=YnViYmxlLXB1YmxpYzoyNzgwNjE1NDEyNjMwMTQwMDA6OTIyMzM3MjAzNjg1NDc3NTgwNzpwdWJsaWM6NzA1NjhkMzQzYzI4YjIyYWUyZjMzY2EyM2U5YTRlNDU6LTE5OTQ2MjQ4MzU1NjUxMDA2NA%3D%3D&burstmediaid=886799034196883000&format=desktop&height=360

And it will use image url which would be similar to-

Thanks!
-HR


#5

Hi I posted a reply on this forum but is not showing up.
I did submit a new request with your suggested changes (We had applicaiton/octet as the content type since we do vieo and photo. But now I have fixed it.)

The url submitted for approval was-https://dev.burst.com/bw/widget_preview.jsp?bubbleId=YnViYmxlLXB1YmxpYzoyNzgwNjE1NDEyNjMwMTQwMDA6OTIyMzM3MjAzNjg1NDc3NTgwNzpwdWJsaWM6NzA1NjhkMzQzYzI4YjIyYWUyZjMzY2EyM2U5YTRlNDU6LTE5OTQ2MjQ4MzU1NjUxMDA2NA%3D%3D&width=480&height=360&format=desktop&burstmediaid=886799034196883000