Обсуждение: Uhm, so, yeah, speaking of /.
Just trying to post, and getting this error message: > Invalid form key: c3pVklZBr9 > > Chances are, you're behind a firewall or proxy, or clicked the Back button to > accidentally reuse a form. Please try again. If the problem persists, and all > other options have been tried, contact the site administrator. Now the facts are: I am not behind a proxy nor did I hit the back button. People who don't use /. all the time might now realize the simple truth: it's a flaky hacky site. Anybody holding it up as an example of a robust high-volume site ought to have their head examined ;-) -- Scott Ribe scott_ribe@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice
On Thu, 2007-05-24 at 19:15 -0600, Scott Ribe wrote:
> Just trying to post, and getting this error message:
>
> > Invalid form key: c3pVklZBr9
> >
> > Chances are, you're behind a firewall or proxy, or clicked the Back button to
> > accidentally reuse a form. Please try again. If the problem persists, and all
> > other options have been tried, contact the site administrator.
>
> Now the facts are: I am not behind a proxy nor did I hit the back button.
>
> People who don't use /. all the time might now realize the simple truth:
> it's a flaky hacky site. Anybody holding it up as an example of a robust
> high-volume site ought to have their head examined ;-)
>
I thought it had to do with letting a form sit around too long and
then /. timing out the state.
That's probably not good anyway: it should at least give you a real
error message. However, they might not consider that a bug.
Regards,
Jeff Davis
> I thought it had to do with letting a form sit around too long and > then /. timing out the state. > > That's probably not good anyway: it should at least give you a real > error message. However, they might not consider that a bug. I didn't let the form sit around at all--didn't think to mention that before. It may well not be related to MySQL at all, the point is simply that although /. is well-known, gets a lot of hits, and works well enough for its intended purpose, it is buggy and is NOT an example of what would be acceptable reliability for most "mission critical" applications. -- Scott Ribe scott_ribe@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice
On Wed, 2007-05-30 at 12:18 -0600, Scott Ribe wrote:
> > I thought it had to do with letting a form sit around too long and
> > then /. timing out the state.
> >
> > That's probably not good anyway: it should at least give you a real
> > error message. However, they might not consider that a bug.
>
> I didn't let the form sit around at all--didn't think to mention that
> before. It may well not be related to MySQL at all, the point is simply that
> although /. is well-known, gets a lot of hits, and works well enough for its
> intended purpose, it is buggy and is NOT an example of what would be
> acceptable reliability for most "mission critical" applications.
>
I was agreeing with you.
I think that's what the "invalid form key" error is supposed to mean,
but it probably happens for all kinds of other cases, too (which is bad
and causes confusion).
I agree that /. not a great example of stability or correctness.
Regards,
Jeff Davis
Jeff Davis wrote:
> On Wed, 2007-05-30 at 12:18 -0600, Scott Ribe wrote:
>>> I thought it had to do with letting a form sit around too long and
>>> then /. timing out the state.
>>>
>>> That's probably not good anyway: it should at least give you a real
>>> error message. However, they might not consider that a bug.
>> I didn't let the form sit around at all--didn't think to mention that
>> before. It may well not be related to MySQL at all, the point is simply that
>> although /. is well-known, gets a lot of hits, and works well enough for its
>> intended purpose, it is buggy and is NOT an example of what would be
>> acceptable reliability for most "mission critical" applications.
>>
>
> I was agreeing with you.
>
> I think that's what the "invalid form key" error is supposed to mean,
> but it probably happens for all kinds of other cases, too (which is bad
> and causes confusion).
>
> I agree that /. not a great example of stability or correctness.
Interesting statement. Question: What would be a great example of
stability of correctness?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
On Wed, 2007-05-30 at 11:41 -0700, Joshua D. Drake wrote:
> > I agree that /. not a great example of stability or correctness.
>
> Interesting statement. Question: What would be a great example of
> stability of correctness?
>
Admittedly, I'm comparing against an ideal. If I get ungraceful errors
on /., that proves to me that it's not perfect.
I haven't had any problems on ebay before, for example, but maybe I just
don't use it enough. Amazon I've only had a problem once, and it was a
very graceful, localized error.
Gmail I had a problem once, but yahoo email has worked flawlessly for me
for a long time.
I'm sure others have had different experiences, and I don't mean to
generalize too much, but if you ask, I would say those other sites are
in a league above slashdot.
Of course, slashdot certainly gets the job done. If I get some error I
usually don't care much, but I would care if I was making a financial
transaction or counting on email.
Regards,
Jeff Davis
Google. And, yes, Google use a modified MySQL for its pigeons.
--
Brandon Aiken
CS/IT Systems Engineer
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Joshua D. Drake
Sent: Wednesday, May 30, 2007 2:41 PM
To: Jeff Davis
Cc: Scott Ribe; PostgreSQL general
Subject: Re: [GENERAL] Uhm, so, yeah, speaking of /.
Jeff Davis wrote:
> On Wed, 2007-05-30 at 12:18 -0600, Scott Ribe wrote:
>>> I thought it had to do with letting a form sit around too long and
>>> then /. timing out the state.
>>>
>>> That's probably not good anyway: it should at least give you a real
>>> error message. However, they might not consider that a bug.
>> I didn't let the form sit around at all--didn't think to mention that
>> before. It may well not be related to MySQL at all, the point is
simply that
>> although /. is well-known, gets a lot of hits, and works well enough
for its
>> intended purpose, it is buggy and is NOT an example of what would be
>> acceptable reliability for most "mission critical" applications.
>>
>
> I was agreeing with you.
>
> I think that's what the "invalid form key" error is supposed to mean,
> but it probably happens for all kinds of other cases, too (which is
bad
> and causes confusion).
>
> I agree that /. not a great example of stability or correctness.
Interesting statement. Question: What would be a great example of
stability of correctness?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
** LEGAL DISCLAIMER **
Statements made in this e-mail may or may not reflect the views and
opinions of Wineman Technology, Inc. or its employees.
This e-mail message and any attachments may contain legally privileged,
confidential or proprietary information. If you are not the intended
recipient(s), or the employee or agent responsible for delivery of
this message to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this e-mail
message is strictly prohibited. If you have received this message in
error, please immediately notify the sender and delete this e-mail
message from your computer.