Closed Bug 852167 Opened 12 years ago Closed 12 years ago

validator fails to retrieve Bangladesh Weather manifest every day

Categories

(Marketplace Graveyard :: Validation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: eviljeff, Unassigned)

References

()

Details

The manifest for Bangladesh Weather (http://mythrobin.com/bangladesh_weather/manifest.webapp) fails during every daily manifest check, but otherwise appears perfectly valid. Can someone look into it and find out what the issue is?
It doesn't validate locally: Summary: ------------------------------ Test failed! Errors: Error: JSON Parse Error The file is missing a comma towards the end.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
That was because I was trying to solve the issue and adding new fields. No success whatsoever. I have corrected the manifest like it was before. Still showing validation error "No manifest was found at that URL. Check the address and try again."
Pinging that URL from Python's urllib2 returns a 403 response from the server: >>> import urllib2 >>> x = urllib2.urlopen('http://mythrobin.com/bangladesh_weather/manifest.webapp', timeout=30) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.6/urllib2.py", line 126, in urlopen return _opener.open(url, data, timeout) File "/usr/lib/python2.6/urllib2.py", line 397, in open response = meth(req, response) File "/usr/lib/python2.6/urllib2.py", line 510, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib/python2.6/urllib2.py", line 435, in error return self._call_chain(*args) File "/usr/lib/python2.6/urllib2.py", line 369, in _call_chain result = func(*args) File "/usr/lib/python2.6/urllib2.py", line 518, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 403: Forbidden Your server is probably blocking spiders. In this case, it's likely due to the default user agent: "Python-urllib/2.6". Tell your webhost to stop blocking that user agent.
You need to log in before you can comment on or make changes to this bug.