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

add note about how cascade OGC httpS layers with QGIS Server #2665

Merged
merged 3 commits into from
Jul 24, 2018

Conversation

gioman
Copy link
Contributor

@gioman gioman commented Jun 3, 2018

No description provided.

@gioman
Copy link
Contributor Author

gioman commented Jun 3, 2018

Possibly (unchecked yet) this is also good to be added to QGIS 3 manual.

@anneb
Copy link

anneb commented Jun 4, 2018

Some comments:
0. IMHO the documented feature in this PR is very important and should be documented ASAP even if documentation is not (yet) perfect

  1. The current version of the PR has a build fail: "Title underline too short"
  2. The new comment is now at the bottom of the documentation page. Shouldn't the HOME FcgidInitialEnv configuration be included by default? This variable seems more 'important' than some of the other included variables
  3. The new documentation in this PR is specific for Apache (www-data, FcgidInitialEnv), but maybe add a comment for NGINX to look at the Apache HOME environment variable configuration?

@DelazJ
Copy link
Collaborator

DelazJ commented Jun 14, 2018

@gioman any reaction to @anneb's comment?

@DelazJ
Copy link
Collaborator

DelazJ commented Jun 29, 2018

ping! Can someone versed in Server details address, if valid, @anneb's comments please? It'd be nice to have the fix online for those that got in this kind of trouble. Thanks.

Cascading OGC layers
--------------------

The QGIS project we plan to use to publish WMS/WFS/WCS layers can of course
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The start of the sentence should be rewrite I think:

A QGIS project can of course contains layers comming from ...

--------------------

The QGIS project we plan to use to publish WMS/WFS/WCS layers can of course
contain layers coming from other (external) OGC servers (regardless of the underlying
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from remote OGC servers


The QGIS project we plan to use to publish WMS/WFS/WCS layers can of course
contain layers coming from other (external) OGC servers (regardless of the underlying
OGC server software used). This way we will effectively **cascade** those layers
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This way QGIS will effectively

through our OGC (QGIS Server based) services.

If the external OGC layers are coming from services that make use of the **HTTPS**
protocol we must take care of some extra QGIS Server configuration. Example for
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we -> you

@yjacolin
Copy link
Member

@anneb could you change the requested changes then we can merge your PR. Thanks!

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

Successfully merging this pull request may close these issues.

None yet

4 participants