Which is why in my original thought, I said "We don't want our error pages to be
"too pretty" unless they can be customized based on the data type requested by
the client." :)
On Oct 8, 2012, at 8:24 AM, Douglas Campos <qmx(a)qmx.me> wrote:
just ask for application/json ;)
On Oct 8, 2012, at 10:22 AM, Kris Borchers wrote:
> But that's what I'm saying. For example, say my app is trying to authenticate
via a REST endpoint. I haven't specified an error page but auth fails and a 401 is
returned. Since it's just a REST call, I don't want an error page but just some
JSON back. I just want to make sure that is possible.
>
> On Oct 8, 2012, at 8:19 AM, Douglas Campos <qmx(a)qmx.me> wrote:
>
>> I mean default error page, when the user doesn't specify one.
>>
>> On Oct 8, 2012, at 10:17 AM, Kris Borchers wrote:
>>
>>> I had the same thought but we should be careful. We don't want our error
pages to be "too pretty" unless they can be customized based on the data type
requested by the client. We have to keep mobile in mind and we don't want to be using
a ton of data just to throw big fancy error pages at the app, especially if it's an
AJAX request or data being sent over a websocket and it won't even be displayed. In
that instance, less would be more.
>>>
>>> On Oct 8, 2012, at 8:13 AM, Douglas Campos <qmx(a)qmx.me> wrote:
>>>
>>>> What about asking our design overlords (cough James Cobb cough) about it?
This is something that if we do right, will help a lot to improve mindshare (beautiful
error pages and consistent l&f).
>>>>
>>>>
>>>> On Oct 8, 2012, at 9:39 AM, Daniel Bevenius wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I wanted to get some input on what you'd like to see on a default
error page in aerogear-controller. This is the page that a user will see if an error
occurs, and no custom error route has been defined.
>>>>> I'm attaching a screenshot of what I'm playing with at the
moment.
>>>>>
>>>>> Some thoughts:
>>>>> 1. Should we be showing the stacktrace at all?
>>>>> 2. Should we have a button which can be used to display the
stacktrace?
>>>>>
>>>>> Any suggestions are as always most welcome.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> /Daniel
>>>>> <ErrorPage.png>_______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev(a)lists.jboss.org
>>>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>> -- qmx
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>> -- qmx
>>
>>
>> _______________________________________________
>> 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
-- qmx
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev