Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


On Fri, Mar 21, 2014 at 5:41 AM, Robinson Tryon
<bishop.robinson@gmail.com> wrote:
On Fri, Mar 21, 2014 at 3:02 AM, rost52 <bugquestcontri@online.de> wrote:
After entering my text in a bug report using
https://www.libreoffice.org/get-help/bug/
I click "SUYBMIT"
and received the message:

Could not match /Bug ([0-9]+)/i on the string returned by the server <head><title>502 Bad
Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.1.19</center> </body>

after clicking the SUBMIT button again I received the message:

Data not yet loaded. Please press submit again in a few seconds.

XP/SP3
Firefox 27.0.1

Hiya :-)

NO REPRO on Ubuntu 12.04.3 + FF 27.0.1. Was able to file a bug w/o
running into 502 Bad Gateway error:
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=76433

Scratch that -- if I try to upload an attachment during the
bug-filling process (kudos to Dennis R. for the hint :-), I can repro
this problem.

See bug 76433 (as above) for details.

Danke,
--R

-- 
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.