542208 - Error im ChangeCol.cgi

Status: RESOLVED INVALID

(Bugzilla :: Bugzilla-General, defect)

Description

[Steffen Hoffmann]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 1.0.3705; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Build Identifier: version 3.4.3

Wird nach der Suche (Suchkriterium unabhängig) die Ansicht der Spalten geändert, so tritt oft eine Fehlermeldung auf. Siehe screenshot. 

(Die Ansicht der Spalten kann durch die Button "Change Columns" geänder werden. Danach ist eine Auswahl der zu darstellenden Spalten möglich.)

Reproducible: Sometimes

Steps to Reproduce:
Wird nach der Suche (Suchkriterium unabhängig) die Ansicht der Spalten geändert, so tritt oft eine Fehlermeldung auf. Siehe screenshot. 

(Die Ansicht der Spalten kann durch die Button "Change Columns" geänder werden. Danach ist eine Auswahl der zu darstellenden Spalten möglich.)
Actual Results:  
Seite kann nicht angezeigt werden.

Expected Results:  
Die Spalten richtig anzeigen

Comment 1

[Frédéric Buclin]

Marc, I habe nicht alles verstanden. Es hat etwas mit colchange.cgi zu tun, aber Ich verstehe nichts mehr. :)

Resolving as invalid unless Marc can reword it in english and the issue is real.

Comment 2

[Marc Schumann [:Wurblzap]]

Steffen, please add the screenshot you mentioned :)
Without the error message, there is no way for us to do anything.

In addition, please specify whether you're using a language pack (German?) and whether its version matches your Bugzilla's version.

Comment 3

[Andreas Milde]

Hello together,

as a colleague of Steffen I am experiencing the same problem.
I will repeat what he wrote in english here:
After a search (doesn't matter for what you search) you can change the colums to display in the buglist. When we do this in our installation sometimes it works correctly, but often it won't. It will just display an error message of the webserver which says: This page is no longer online.


We are not using a language pack, the Bugzilla installation (v3.4.3) is running with the english interface on a CentOS-machine.

The following is the complete URL (I changed the servername to SERVERNAME here) if the columnchange fails:

https://SERVERNAME/colchange.cgi?rememberedquery=bug_status%3DUNCONFIRMED%26bug_status%3DNEW%26bug_status%3DANALYSIS%26bug_status%3DSPECIFICATION%26bug_status%3DIMPLEMENTATION%26bug_status%3DMODULE%2520TEST%26bug_status%3DSYSTEM%2520TEST%26bug_status%3DRFRS_READY%2520FOR%2520RELEASE%2520SOLVED%26bug_status%3DRFRT_READY%2520FOR%2520RELEASE%2520TOLERATED%26bug_status%3DRFRE_READY%2520FOR%2520RELEASE%2520ECU%26bug_status%3DRELS_RELEASED%2520SOLVED%26bug_status%3DRELT_RELEASED%2520TOLERATED%26bug_status%3DRELE_RELEASED%2520ECU%26bug_status%3DRejected%26bug_status%3DDuplicate_%26bug_status%3DChange%2520Request%2520Needed%26content%3Derror%26product%3D%26query_format%3Dspecific%26query_based_on%3D&selected_columns=bug_severity&selected_columns=priority&selected_columns=op_sys&selected_columns=assigned_to&selected_columns=bug_status&selected_columns=resolution&selected_columns=short_desc&selected_columns=version&selected_columns=estimated_time&selected_columns=remaining_time&selected_columns=actual_time&selected_columns=percentage_complete&splitheader=0
(I tried to add the columns Version, Orig.Est., Hours Left, Actual Hours and % Complete to the default settings here)


If the change works correctly the URL points to:
https://SERVERNAME/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ANALYSIS&bug_status=SPECIFICATION&bug_status=IMPLEMENTATION&bug_status=MODULE%20TEST&bug_status=SYSTEM%20TEST&bug_status=RFRS_READY%20FOR%20RELEASE%20SOLVED&bug_status=RFRT_READY%20FOR%20RELEASE%20TOLERATED&bug_status=RFRE_READY%20FOR%20RELEASE%20ECU&bug_status=RELS_RELEASED%20SOLVED&bug_status=RELT_RELEASED%20TOLERATED&bug_status=RELE_RELEASED%20ECU&bug_status=Rejected&bug_status=Duplicate_&bug_status=Change%20Request%20Needed&content=error&product=&query_format=specific&query_based_on=&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cpercentage_complete
(I just added the % complete column to the default in this try)

The problem occurs quite often and it seems to happen everytime we change several columns (more than 4 or 5) at once but it happens also if we change only one or two columns.

I have attached the screenshot Steffen metioned, but I guess it won't help you much because it is an error message of our server which forwards the http connection to the server to a secure https connection.

Tests on a virtual machine with a different installation (on Windows XP) did bring the same errors. These tests were made without https, so I guess the problem is somewhere in the colchange.cgi?

When I checked the http traffic I got the following behavior:
on a successful try 
after the call: 
1)https://SERVERNAME/colchange.cgi?bug_status= ....(and so on) he calls:
2)https://SERVERNAME/js/change-columns.js then he gets some Icons from the skins folder and afther that he calls:
3)https://SERVERNAME/colchange.cgi?rememberedquery=bug_status%3DUNCONFIRMED...
And then the buglist.cgi is called again.

If it doesn't work it is different:
1)https://SERVERNAME/colchange.cgi?bug_status=UNCONFIRMED...
2)https://SERVERNAME/colchange.cgi?rememberedquery=bug_status%3DUNCONFIRMED... --> here he gets the HTTP-Code 404 Not found

The step with "change-columns.js" is not found in this communication.

I hope these informations will help to find a solution.

Comment 4

[Andreas Milde]

Attachment: Screenshot of the error message

Comment 5

[Frédéric Buclin]

(In reply to comment #3)
> it is an error message of our server which forwards the http
> connection to the server to a secure https connection.

I suspect this could be the problem.

Comment 6

[Andreas Milde]

(In reply to comment #5)
> (In reply to comment #3)
> > it is an error message of our server which forwards the http
> > connection to the server to a secure https connection.
> I suspect this could be the problem.

We thought about this, but some tests with a bugzilla installation on a virtual machine (without any forwarding or https) got the same errors too.