Status

()

Firefox
Untriaged
RESOLVED INCOMPLETE
6 years ago
3 years ago

People

(Reporter: sunita, Unassigned)

Tracking

({regression, testcase})

16 Branch
x86
Windows 7
regression, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 680330 [details]
Error1.jpg

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121024073032

Steps to reproduce:

We have an e commerce website based on Magento and we are currently using this version 1.5. Now we have been uploading image on our magento from backend since mozilla 13 branch and now we are using  mozilla 16 branch. So, I was trying to upload an image through magento admin panel.


Actual results:

Earlier we used to upload our images and they had been successfully uploaded on our server. But when I tried uploading the image on your mozilla 15 and 16 branch, I got an error stating that 
"(My Image name) SSL Error: Invalid or self-signed certificate" or
"Upload HTTP error" (see attached file)


Expected results:

The image should have been successfully uploaded as earlier this wasn't the case. Earlier we thought our magento version is not compatible with ur browser but interestingly I am able to upload my images in magento from chrome. So I believe the issue is not from our Magento panel but its a browser issue.
Looking forward to the answer!
Do you upload via https ?
Is it possible that your certificate contains a MD5 hash ?
Firefox stopped supporting this kind of certificate because they are insecure.

Comment 2

6 years ago
Matthias: Setting the needinfo flag is highly welcome.
Flags: needinfo?(sunita.rawat)
(Reporter)

Comment 3

6 years ago
hi,
Sorry for replying late as I had a tight schedule!

@Matthias: yes, I tried uploading via https but the problem is still the same!!
Also, please let me know how do i check out if my certificate contains a MD5 hash??
Flags: needinfo?(sunita.rawat)
Please open about:config (enter as URL in Firefox), confirm the warning, enter md5 in the top filter bar and switch security.enable_md5_signatures from false to true with a doubleclick on the name.

Now try again to upload the image.
Don't forget the change it back to false after your test !
Flags: needinfo?(sunita.rawat)
(Reporter)

Comment 5

6 years ago
(In reply to Matthias Versen (Matti) from comment #4)
> Please open about:config (enter as URL in Firefox), confirm the warning,
> enter md5 in the top filter bar and switch security.enable_md5_signatures
> from false to true with a doubleclick on the name.
> 
> Now try again to upload the image.
> Don't forget the change it back to false after your test !

hey,

Just followed the steps written above. The problem still remains the same.
I wonder if this is the case with other e-comm websites! I'm sure of the Magento though.
Flags: needinfo?(sunita.rawat)
There is not much that we can do as this is a non public page unless someone else has an idea.
(Reporter)

Comment 7

6 years ago
I m sure there must be something because this wasn't the case with Mozilla 13 and 14 branch.
I see only one option at the moment but you would have to do some work.

We have an automated tool for a regression range search.
The tool downloads nightly developers builds and let you test this builds.
After each tested build you have answer the question if the build is good (no bug) or bad (you can see the bug). After ~8 tested builds the tool will show the last good and the first bad build. With this information we can look at the changes between those 2 builds.

The tool is here: http://mozilla.github.com/mozregression/
Example usage: mozregression --good=2012-01-01 --args="http://example.org"

Comment 9

5 years ago
(In reply to Matthias Versen [:Matti] from comment #8)
> I see only one option at the moment but you would have to do some work.
> 
> We have an automated tool for a regression range search.
> The tool downloads nightly developers builds and let you test this builds.
> After each tested build you have answer the question if the build is good
> (no bug) or bad (you can see the bug). After ~8 tested builds the tool will
> show the last good and the first bad build. With this information we can
> look at the changes between those 2 builds.
> 
> The tool is here: http://mozilla.github.com/mozregression/
> Example usage: mozregression --good=2012-01-01 --args="http://example.org"
Flags: needinfo?(sunita.rawat)
Keywords: regression, regressionwindow-wanted, testcase
Whiteboard: [closeme 2013-03-01]

Comment 10

5 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Flags: needinfo?(sunita.rawat)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2013-03-01]
Keywords: regressionwindow-wanted
You need to log in before you can comment on or make changes to this bug.