Bug 147233

Summary:	send-pr fails with HTTP error 417 in Opera 10.10 for Linux
Product:	Documentation	Reporter:	Chris Tandiono <chris.tandiono>
Component:	Books & Articles	Assignee:	Bugmeister <bugmeister>
Status:	Closed Overcome By Events
Severity:	Affects Only Me
Priority:	Normal
Version:	Latest
Hardware:	Any
OS:	Any

Description Chris Tandiono 2010-05-30 21:00:11 UTC

I get a 417 error attempting to submit a problem report in Opera 10.10 for Linux. However, it still says "thanks for submitting", so it's not clear if the pr has been submitted or not.

Fix should either remove the thank you notice when there's an error, or fix the error.

Screenshot is available but too large to be attached.

Fix: 

Unknown, but should involve removing the error message or removing the thank you message.

Since the pr seems to have been submitted, removing the error message is probably best.
How-To-Repeat: Attempt to submit a pr with Opera 10.10 in Linux.

Comment 1 Johann Kois freebsd_committer

2010-06-17 15:03:46 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is there a specific reason why you submit a *FreeBSD* problem report
from a *Linux* system and usk us to test this on a *Linux* box?

- -- 
 Johann Kois
 jkois(at)FreeBSD.org
 FreeBSD Documentation Project
 FreeBSD German Documentation Project - https://doc.bsdgroup.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwaK0IACgkQ/rDr791hwthK1gCdHX2LetjkvBePZSSxhqbqkvoS
zqQAn0YaxOE+R7DpHnnKN6lEOz8aofKd
=yZqr
-----END PGP SIGNATURE-----

Comment 2 Johann Kois freebsd_committer

2010-06-17 15:04:41 UTC

State Changed
From-To: open->feedback

Change the status to "feedback" needed.

Comment 3 Johann Kois freebsd_committer

2010-06-18 10:06:45 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The original sender of the PR provided the following feedback:

On 18.06.2010 00:11, Chris Tandiono wrote:
> Not asking anyone to test it with any particular OS or even any
> particular version of Opera or, indeed, with any particular browser at
> all. There simply shouldn't be any reason to display an error message,
> implying failure, yet also display a "Thank you" message, implying
> success. The point I'm trying to make is that the feedback could lead
> users to create duplicate PRs, which I ended up doing.
>
> Chris


- -- 
 Johann Kois
 jkois(at)FreeBSD.org
 FreeBSD Documentation Project
 FreeBSD German Documentation Project - https://doc.bsdgroup.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwbNyUACgkQ/rDr791hwtiNmACfe082GBTjAnOxYMLCONd5bxKt
9mgAnjAEwKriAHF1dYk+oXkQxFBWRJMR
=SGNu
-----END PGP SIGNATURE-----

Comment 4 Ceri Davies 2010-06-23 12:02:50 UTC

The 417 code may very well come from a proxy inbetween the FreeBSD servers
and your system.

RFC2616 says that a 417 error code MUST be included if an Expect header
cannot be met, so there is a reason to do so.  See
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.20

Ceri

Comment 5 Chris Tandiono 2010-06-23 21:20:29 UTC

That would make sense if there were one or more proxies between myself
and the FreeBSD servers, which to my knowledge there is not.

If RFC 2616 requires reporting a 417 error code then that's what must be
done.  Although it might be nice to also include a note saying that the
PR submission was successful anyway.

Chris

On Wed, 2010-06-23 at 12:02 +0100, Ceri Davies wrote:
> The 417 code may very well come from a proxy inbetween the FreeBSD servers
> and your system.
> 
> RFC2616 says that a 417 error code MUST be included if an Expect header
> cannot be met, so there is a reason to do so.  See
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.20
> 
> Ceri
> 
>

Comment 6 Mark Linimon freebsd_committer

2010-08-04 04:23:01 UTC

Responsible Changed
From-To: freebsd-www->bugmeister

bugmeister territory.

Comment 7 Marcus von Appen freebsd_committer

2014-11-22 17:53:22 UTC

Closing this, since send-pr is obsolete for now.