Bug 146106 - Loading graphic with XGraphicProvider::queryGraphic from https: CRL validation does not use proxy setting
Summary: Loading graphic with XGraphicProvider::queryGraphic from https: CRL validatio...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
7.1.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Options-Dialog
  Show dependency treegraph
 
Reported: 2021-12-07 20:09 UTC by pierre.sauter
Modified: 2024-12-24 05:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pierre.sauter 2021-12-07 20:09:24 UTC
Description:
When loading an image from a https URL, the CRL check tries to connect to crl.root-x1.letsencrypt.org.edgekey.net directly instead of going through the configured proxy, resulting in a timeout.

Steps to Reproduce:
1. Be behind a http proxy and configure it in Libreoffice
2. Load an image from a https URL with XGraphicProvider::queryGraphic

Actual Results:
CRL check of the https certificate is tried directly resulting in a timeout

Expected Results:
CRL should be loaded via the http proxy


Reproducible: Always


User Profile Reset: No



Additional Info:
The CRL check seems to have been introduced sometime around 7.0. We recently upgraded from 6.4.7-0ubuntu0.20.04.1 to 7.1.7-0ubuntu0.21.04.1~bpo20.04.1 when that version landed in Ubuntu 20.04 backports. Before that it was working as expected. Also changing the URL to http resolves the issue in 7.1.7
Comment 1 Sanchu Manthiram Shanmugam 2022-12-03 06:16:33 UTC
There seems to be some issue in setting the Proxy configurations. 

While they may be better addressed as a separate bug, this issue warrants to be investigated further.
Comment 2 Sanchu Manthiram Shanmugam 2022-12-03 07:02:29 UTC
the above comment was due to this bug -> https://bugs.documentfoundation.org/show_bug.cgi?id=33697
Comment 3 QA Administrators 2024-12-04 03:11:59 UTC
Dear pierre.sauter,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug