On Thu, Aug 21, 2008 at 11:44 AM, Raoul Snyman <[EMAIL PROTECTED]> wrote:
> I did this, but when I ran "paster make-config
> config.ini", I got the following message:
> No paste_deploy_config.ini_tmpl found
Hmph. Found out why it couldn't find it... I had somehow managed to
add a space at the en
> You're using *var with a default value, and the magic *path_info on
> top of that. All of these could interact in unexpected ways. It
> would be better to make two or three specific routes for these cases,
> and to use named routes for generation. That minimizes the ambiguity.
> So do someth
Hello guys,
Do you mind if I chime in? I agree that verify should not use 400 HTTP
status code to indicate failure of verifying variable values. I don't
think that even an failure to parse HTTP request body should be
indicated in such a way as long as there were no failure on HTTP
protocol level.
On Tue, 2008-08-19 at 11:43 +0200, Lawrence Oluyede wrote:
> I disagree. TCP is the transport protocol (which resides at the
> transport level of the stack).
> HTTP is an application protocol (which resides on top of the stack),
> and I'm pretty sure that
> the creators of HTTP intended to use 40
I'll admit at the forefront, I'm not a fan of the extreme
'restification' of the web the way the rails evangelists and followers
have pushed for, or the 'restful web services' crowd.
http is the transport protocol. its in the name -- "Hypertext Transfer
Protocol"
throwing a 400 on a form error
How can I submit a bug to beaker? The trac requests a password :)
[]'s
- Walter
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroup
On Fri, 2008-08-22 at 18:43 -0700, Jonathan Vanasco wrote:
> question though -- what if the @validate received the right params,
> but there was a db error or some other server error. does that become
> another 4xxx code in your system, or are they all lumped into the same
> concept. how are tho
On 8/23/08, Alex wrote:
>
> Beside, forcing browser to show its standard error
> page for 400 error code when user simply made a mistake entering e-
> mail address or phone number is the straightest way to scare your
> users to death.
>
No, on modern browsers, your form validation error page
On Aug 22, 2008, at 7:44 PM, Sok Ann Yap wrote:
By the way, Django has a rest plugin that is hardcoded to return 400
on form validation failures [2]. Struts has a rest plugin that by
default returns 400 on form validation failures [3]. Pylons already
has a wonderful rest controller. I am merely
On Fri, Aug 22, 2008 at 6:43 PM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
>
> I'll admit at the forefront, I'm not a fan of the extreme
> 'restification' of the web the way the rails evangelists and followers
> have pushed for, or the 'restful web services' crowd.
Remember that REST is just a
10 matches
Mail list logo
