Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Firefox is not allowing me to upload files to our internal sites on https

  • 1 wótegrono
  • 1 ma toś ten problem
  • 17 naglědow
  • Slědne wótegrono wót cor-el

Nanda Kumar
Nanda Kumar
more options

At least since last 3 months as far as I can remember, file uploads to our internal sites which use https are not working on firefox browser. I thought it is really a certificate issue or something else. But I tried uploading the same file to same site on IE and it worked. For example, we have our internal wiki site. I could browse and edit pages and do all other things on firefox. But when it comes to uploading a file, after clicking on 'upload' button, firefox returns an error which includes error code "SEC_ERROR_OCSP_OLD_RESPONSE". On other site which is our internal bugzilla, upload didn't work but this time there was no error code as far as I can remember. It is similar message on the lines of 'Your connection is not secure'. Then I tried uploading the file on IE and it worked. Sometimes, retrying it 2 or 3 times works. On one day I saw after retrying 3 times by clicking 'RETRY' button after the error message, file actually got uploaded twice to the wiki. Today after sometime, I tried uploading the same file to bugzilla(by going back to upload page by clicking on <- back arrow) and it worked this time. There is some problem for sure.

At least since last 3 months as far as I can remember, file uploads to our internal sites which use https are not working on firefox browser. I thought it is really a certificate issue or something else. But I tried uploading the same file to same site on IE and it worked. For example, we have our internal wiki site. I could browse and edit pages and do all other things on firefox. But when it comes to uploading a file, after clicking on 'upload' button, firefox returns an error which includes error code "SEC_ERROR_OCSP_OLD_RESPONSE". On other site which is our internal bugzilla, upload didn't work but this time there was no error code as far as I can remember. It is similar message on the lines of 'Your connection is not secure'. Then I tried uploading the file on IE and it worked. Sometimes, retrying it 2 or 3 times works. On one day I saw after retrying 3 times by clicking 'RETRY' button after the error message, file actually got uploaded twice to the wiki. Today after sometime, I tried uploading the same file to bugzilla(by going back to upload page by clicking on <- back arrow) and it worked this time. There is some problem for sure.

Wšykne wótegrona (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

This usually indicates a problem with OCSP stapling where the server sends an expired (cached) OCSP response.

You can try to disable OCSP Stapling temporarily by toggling this pref to false on the about:config page to see if that has effect.

  • security.ssl.enable_ocsp_stapling = false

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

It is best to reset this pref via the right-click context menu to true once you are done with accessing an affected website since this is a security feature.

Note that this should be fixed on affected server(s) and you can contact your IT department to look into this. Some months ago there had been a similar issue on Microsoft Outlook internet servers that took quite some effort for Microsoft to repair all their servers.

See also:

Wót cor-el změnjony