[ECODP-dev] Last update date as API call

John Glover john.glover at okfn.org
Tue Aug 27 09:54:13 UTC 2013


Hi Dimitrios,

Thanks, yes it looks good now.

Regards,
John


On 27 August 2013 11:45, Dimitrios Mexis <dimitrios.mexis at tenforce.com>wrote:

>  Hi John,
>
> Thank you for the link, very helpfull. I parse the response there, and
> gives me green.
>
> Regards
> Dimitrios
>
>
> On 27/08/2013 11:31, John Glover wrote:
>
> Hi Dimitrios,
>
>  Sorry, perhaps my email was a bit unclear - the surrounding single
> quotes were not supposed to be included, as of course this is still not
> valid JSON. There is a useful tool here: http://jsonlint.com/
>
>  Regards,
> John
>
>
> On 27 August 2013 11:28, Dimitrios Mexis <dimitrios.mexis at tenforce.com>wrote:
>
>>  now ?
>>
>>
>> On 27/08/2013 11:19, John Glover wrote:
>>
>> Hi Dimitrios,
>>
>>  Thanks, it is now returning the date in the correct format (on the test
>> server), and the content-type is now application/json. However, you are no
>> longer returning valid JSON. Can you please return a string of the form:
>> '{"lastUpdate": "DD/MM/YYYY"}'.
>>
>>  Regards,
>> John
>>
>>
>> On 27 August 2013 10:51, Dimitrios Mexis <dimitrios.mexis at tenforce.com>wrote:
>>
>>>  Hello John,
>>>
>>> Thank you for the feedback,
>>> I removed the overall json output, and return it as a dump string text.
>>> I test it on browser, and is application/json for sure. But not JSON
>>> output.
>>>
>>> can you check now again on 212.xxx ?
>>>
>>>
>>> On 27/08/2013 9:58, John Glover wrote:
>>>
>>> Hi Dimitrios,
>>>
>>>  I have a couple of comments about this API call:
>>>
>>>  - could you please return the date in the correct format? It is
>>> currently returning DD-MM-YYYY but should be DD/MM/YYYY.
>>> - (small issue) it returns JSON but the content-type header is set as
>>> text/html instead of application/json which seems like an error.
>>>
>>>  Regards,
>>> John
>>>
>>>
>>> On 20 August 2013 17:17, Dimitrios Mexis <dimitrios.mexis at tenforce.com>wrote:
>>>
>>>>  Hi Darwin,
>>>>
>>>> as we have some problems with the network and dns translation, I put a
>>>> new rule in /etc/nginx which directs the call to the API, to another Drupal
>>>> version that carries this API call.
>>>>
>>>> Normally it must be sufficient.
>>>>
>>>> Thanks,
>>>> Dimitrios
>>>>
>>>>
>>>> On 20/08/2013 16:46, Darwin Peltan wrote:
>>>>
>>>> Hi Dimitrios,
>>>>
>>>>  This API doesn't seem to be present on the test site (212.xx) -
>>>> Please could you install it there as well ASAP.
>>>>
>>>>  Thanks,
>>>>
>>>>  Darwin
>>>>
>>>>  *Darwin Peltan*
>>>>
>>>> *Project Manager  |  skype: darwinp  |  twitter: @darwin<http://twitter.com/darwin>
>>>> *
>>>>
>>>> *The Open Knowledge Foundation <http://okfn.org/>*
>>>>
>>>> *Empowering through Open Knowledge*
>>>>
>>>> *http://okfn.org/  |  @okfn <http://twitter.com/OKFN>  |  OKF on
>>>> Facebook <https://www.facebook.com/OKFNetwork>  |  Blog<http://blog.okfn.org/> |
>>>> Newsletter <http://okfn.org/about/newsletter>*
>>>> *
>>>> CKAN | http://ckan.org | @ckanproject <http://twitter.com/ckanproject>|open source data management platform
>>>> *
>>>>
>>>>
>>>> On 12 August 2013 14:37, Dimitrios Mexis <dimitrios.mexis at tenforce.com>wrote:
>>>>
>>>>>  Hi,
>>>>>
>>>>> check
>>>>>
>>>>> curl http://odp.tenforce.com/api/getUpdatedDate
>>>>>
>>>>>
>>>>> Regards
>>>>> Dimitrios
>>>>>
>>>>> _______________________________________________
>>>>> Ecodp-dev mailing list
>>>>> Ecodp-dev at lists.okfn.org
>>>>> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Ecodp-dev mailing listEcodp-dev at lists.okfn.orghttp://lists.okfn.org/mailman/listinfo/ecodp-dev
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130827/f2458991/attachment.html>


More information about the ecodp-dev mailing list