Closed Bug 384270 Opened 17 years ago Closed 17 years ago

Can't submit bugs under Jira

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: daniel.keeley, Unassigned)

References

Details

(Keywords: regression)

Attachments

(2 files)

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a5) Gecko/20070606 GranParadiso/3.0a5

URL not entered as it's an internal system.  But raising any bug under the software tracking tool - Jira, gives an error on the 2nd step pasted below.

So it seems the session tracking or cookie management in Firefox 3 is broken.  Other websites i've visited all seem to work ok so far.  Jira works fine with Firefox 2, Safari and IE6/IE7.

Step 2 of 2: Enter the details of the issue...
Errors

    * Error instantiating webwork.multipart.parser.class: com.atlassian.jira.web.JiraMultipartRequestWrapper(original message: null)

You have not selected a valid project to create an issue in.



Reproducible: Always

Steps to Reproduce:
1.Login to Jira
2.Create a new issue
3.fill in form, click next, bang.


Expected Results:  
Jira bug should be created!
Ludo, can you reproduce this?
Status: UNCONFIRMED → NEW
Ever confirmed: true
This as been cross filed at  atlassian as http://jira.atlassian.com/browse/JRA-12916.
If this is something on our end as that bug claims, can we get the output of a POST Multi-Part HTTP request using the latest trunk nightly? Ludo was going to do this, but the Jira install he has access to uses SSL, which makes it impossible.

(Also, if someone's feeling really adventurous, a regression range would be nice.)
Keywords: regression
Product: Firefox → Core
QA Contact: general → general
Whiteboard: [needs-regression-range]
Version: unspecified → Trunk
Flags: blocking1.9?
Is this what you are after?
I compared this to firefox 2.0.0.4 and the request parameters look identical!
Actually if you compare the two the one thing that stands out is that firefox 3, has [ Content-Type: text/plain; charset=UTF-8 ] for each parameter where firefox 2 did not specify the content-type.
Matthew, I'm unclear what this build is: Nightly build 19/06/2004

Are you saying the build is from June 19, 2004? I'm guessing that's a typo (s/2004/2007), but just want to confirm. Can you look for a regression range for this and determine when the change was made to add the "Content-Type" info?
Component: General → HTML: Form Submission
QA Contact: general → form-submission
Sorry I can't type was indeed 19/06/2007 i.e. that day.

I'm afraid I'm not a Mozilla developer and I'm unfamiliar with the term 'regression range'. Did try to google it and search the Mozilla docs!

If your able to explain or post a link and It won't take too long i'm happy to give it a go. Would you want it with the new latest nightly build?

(In reply to comment #7)
> I'm afraid I'm not a Mozilla developer and I'm unfamiliar with the term
> 'regression range'. Did try to google it and search the Mozilla docs!

"Regression Range" is something that helps finding out when the problem started to happen - so QA, or the developers can find what change broke the behavior. Basically it means trying older nightly builds until you find one that works. and then give us the build ID of the last one that worked and of the first one that is broken.
If the problem is simply that we add a content-type header to form submissions then that seems like something that should be fixed in Jira. W/o access to a Jira installation where we can test this and see what's happening there's not a whole lot we can do here as far as debugging goes on our end.

If someone could find what nightly build this broke in (i.e. the regression range) that would be extremely helpful.
Guys, if you need a JIRA installation you can download from the website and get an eval license that's good for 30 days. We will provide any extensions as required.

Regarding whether it is probably a JIRA problem we are of the opinion it probably is if the content type specification is the only thing that has changed. Could you please indicate though why this was added - as FF3 is the only browser to implement this.
The change that broke JIRA was intentional (read all about it in the bug referenced above), and given that we have yet to hear about it causing any other problems, we won't be going back on that change. Marking this bug INVALID.
Status: NEW → RESOLVED
Closed: 17 years ago
Flags: blocking1.9? → blocking1.9-
Resolution: --- → INVALID
> and given that we have yet to hear about it causing any other problems, we won't be going back on that change.

As mentioned in bug 387991, other sites suffering from this are:
http://apply.aquent.com
http://episteme.arstechnica.com/eve (the Ars Technica forums)
Apparently all eve community sites are effected by this from what I can tell. A google search for "eve community" returns 1.58 million results. 

I have posted a bug report to their support forums. 
http://support.evecommunity.com/eve/forums/a/tpc/f/2311048/m/54810961863
I just reopened bug 116346 which is what caused this problem in the first place. Please take any further discussion about this into that bug.
Blocks: 116346
Whiteboard: [needs-regression-range]
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: