Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: content symbol not encoded to utf-8 when accessing app through https with ssl cert #5285

Open
1 task
cfsgarcia opened this issue Jan 28, 2025 · 1 comment

Comments

@cfsgarcia
Copy link
Contributor

What is the bug? (in English)

I don't know what to make of this issue. It's very strange.

When I access the app in http the table of content expanders show as expected:
Image

However, when accessing the same app, same server, same config but through https with ssl certificates, it doens't seem to encode the character to utf-8:
Image
Doesn't seem to convert it into the expected triangle: lizmap/www/assets/css/map.css::lizmap-treeview div.expandable::before
Image

Steps to reproduce the issue

Switch from htttp:// to https://

Versions, safeguards, check summary etc

Lizmap Web Client 3.8.1
qGIS Server 3.34.6

Check Lizmap plugin

  • I have done the step just before in the Lizmap QGIS desktop plugin before opening this ticket. Otherwise, my ticket is not considered valid and might get closed.

Operating system

Ubuntu 22.04.2 LTS

Browsers

Chrome

Browsers version

Version 132.0.6834.111 (Official Build) (64-bit)

Relevant log output

@cfsgarcia cfsgarcia added the bug label Jan 28, 2025
@Gustry
Copy link
Member

Gustry commented Jan 29, 2025

I don't know if it's an issue related to Lizmap it self.
As you can notice, we do not reproduce the issue : https://demo.lizmap.com/lizmap/index.php/view/map?repository=features&project=land_use

Maybe it's more a question on https://stackoverflow.com/ to have an idea about web server ? Nginx or Apache or ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants