Sorry,
Yes, I am try updating a contact and the server responded w/ status code 500
* Adding handle: conn: 0x7ff159003000
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7ff159003000) send_pipe: 1, recv_pipe: 0
* About to connect() to
PUT /rest/contacts/7 HTTP/1.1
User-Agent: curl/7.30.0
Host:
quickstarts-edewit.rhcloud.com
Cookie:
JSESSIONID=zugucP2LNHLbCNNOwBrD3mx6.quickstarts-edewit.rhcloud.com
Accept: application/json
Content-type: application/json
Content-Length: 120
* upload completely sent off: 120 out of 120 bytes
< HTTP/1.1 500 Internal Server Error
< Date: Mon, 02 Jun 2014 12:04:59 GMT
< Content-Type: text/html;charset=ISO-8859-1
< Content-Length: 80
< Connection: close
<
* Closing connection 0
<html><head><title>Error</title></head><body>Internal
Server Error</body></html>
On Mon, Jun 2, 2014 at 4:39 AM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
What is the issue you are having and what are you trying to do (issue
just
with the update?) ?
On Fri, May 30, 2014 at 8:48 PM, Daniel Passos <daniel(a)passos.me> wrote:
> Someone know that I am doing wrong?
> Login
>
> curl -v -b cookies.txt -c cookies.txt \
> -H "Accept: application/json" \
> -H "Content-type: application/json" \
> -u "myuser:mypass" \
> -X GET
http://quickstarts-edewit.rhcloud.com/rest/security/user/info
>
> Update Contact
>
> curl -v -b cookies.txt -c cookies.txt \
> -H "Accept: application/json" \
> -H "Content-type: application/json" \
> -X PUT \
> -d
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
"birthDate":"2001-03-24"}' \
>
http://quickstarts-edewit.rhcloud.com/rest/contacts/7
>
> — Passos
>
>
>
> On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
> wrote:
>
>> Since we changed the use case for the Push part (now we broadcast) ,
>> passing a alias to UPS is not relevant anymore. For the login it's indeed
>> "loginName" to be passed in the auth header along with the password.
>>
>>
>>
>> On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
>>
>>> To register I send "userName" and the login response
"loginName"?
>>>
>>> -- Passos
>>>
>>>
>>>
>>> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
>>> wrote:
>>>
>>>> Sure !
>>>> This is just a version to ease the client development.
>>>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>>>> In the mean time we can track all of this with
>>>>
https://issues.jboss.org/browse/AGPUSH-596
>>>>
>>>> Thx for the comment !
>>>> Sebi
>>>>
>>>>
>>>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira
<bruno(a)abstractj.org>
>>>> wrote:
>>>>
>>>>> If your idea is to be secure, please make sure to use HTTPS and
>>>>> enforce
>>>>> users to be redirected. We did it in the past with HSTS on AG
>>>>> Security,
>>>>> might not be hard to copy & paste.
>>>>>
>>>>> Sebastien Blanc wrote:
>>>>> > And because I love you, I deployed on OpenShift a version of
this
>>>>> secured
>>>>> > backend to ease the development of the clients !
>>>>> >
>>>>> > If you browse to
http://contacts-sblanc.rhcloud.com/ you will
even
>>>>> see the
>>>>> > mobile web client. This deployed version contains also the Push
>>>>> Message
>>>>> > endpoint.
>>>>>
>>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev