See https://github.com/tillnagel/unfolding/issues/61 for the assumed reason (on Google's side).
Alas, no immediate solution. If you can confirm it's the same reason on your side you might want to try switching to another Java version.



Hi fabwoj! Haven't seen this thread before, but responded to you via e-mail. This is more to shift the discussion for others to read. Can you try and check in your Command/Terminal two things: Do the CURL commands result in the same responses as for me? And re-check if you are really using Java 1.7, i.e. if the user-agent is set as such.

Hi tillnm,

About the java version :
When I go to controlPanel / java  and tab java I can see that I use java 1.7 . Is that the correct way to check the java version I use ?

About CURL :
I don't know anything about this. I tried to understand with google informations but it's not clear for me.
Can you give me more explanation about the way to use CURL ?

Thank you for all.
 

Hi tillnm,

I find the way to use curl. I downloaded an exe there :
http://curl.haxx.se/dlwiz/?type=bin

The result for curl -v -I -H "User-Agent: Java/1.6.0_45" " http://mt1.google.com/vt/lyrs=m@116&hl=de&x=3&y=0&z=2&s=Galileo"  is :

* About to connect() to mt1.google.com port 80 (#0)
*   Trying 173.194.40.195...
* connected
* Connected to mt1.google.com (173.194.40.195) port 80 (#0)
> HEAD /vt/lyrs=m@116&hl=de&x=3&y=0&z=2&s=Galileo HTTP/1.1
> Host: mt1.google.com
> Accept: */*
> User-Agent: Java/1.6.0_45
>
< HTTP/1.1 403 Forbidden
HTTP/1.1 403 Forbidden
< Content-Length: 1207
Content-Length: 1207
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8
< Date: Mon, 06 May 2013 07:59:15 GMT
Date: Mon, 06 May 2013 07:59:15 GMT
< Server: GFE/2.0
Server: GFE/2.0

<
* Connection #0 to host mt1.google.com left intact
* Closing connection #0

The result for curl -v -I -H "User-Agent: Unfolding via Java/1.6.0_45" " http://mt1.google.com/vt/lyrs=m@116&hl=de&x=3&y=0&z=2&s=Galileo" is :

* About to connect() to mt1.google.com port 80 (#0)
*   Trying 173.194.34.38...
* connected
* Connected to mt1.google.com (173.194.34.38) port 80 (#0)
> HEAD /vt/lyrs=m@116&hl=de&x=3&y=0&z=2&s=Galileo HTTP/1.1
> Host: mt1.google.com
> Accept: */*
> User-Agent: Unfolding via Java/1.6.0_45
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Mon, 06 May 2013 08:04:54 GMT
Date: Mon, 06 May 2013 08:04:54 GMT
< Expires: Mon, 06 May 2013 08:04:54 GMT
Expires: Mon, 06 May 2013 08:04:54 GMT
< Cache-Control: private, max-age=3600
Cache-Control: private, max-age=3600
< Access-Control-Allow-Origin: *
Access-Control-Allow-Origin: *
< Content-Type: image/png
Content-Type: image/png
< X-Content-Type-Options: nosniff
X-Content-Type-Options: nosniff
< Server: paintfe
Server: paintfe
< Content-Length: 6098
Content-Length: 6098
< X-XSS-Protection: 1; mode=block
X-XSS-Protection: 1; mode=block
< X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN

<
* Connection #0 to host mt1.google.com left intact
* Closing connection #0



I don't really understand the results. Tell me what you think about them ?

Thanks

Fabrice

Hi,

I understood many things :

1- to get the java version used : System.getProperty("java.version")
Under my processing 1.5.1 the java embedded  is 1.6.0_24. GoogleMap don't want to work with this version of java.

2- When you export as an application your sketch built with processing 1.5.1, you can get maps from google if your version of java is 1.7 in the program Files folder.

3- I downloaded processing 1.5.1 without java. you can get maps from google if your version of java is 1.7 in the program Files folder.

Hope I'am clear enough.


Thank you.

Thanks for the follow-up! Great that you investigated it further.

And while this certainly is useful for others and a work around, it still seems to be rather tedious for developing if one always has to export it before test running the app. Unfortunately, I don't see a fast real solution (as we are using Processing's internal loadImage method which does not allow to set the user-agent header).

Others, please comment if you have the same issue, so we might bump this up on our side.