Jump to content

Recommended Posts

Posted
4 minutes ago, Maxxius said:

And what prevents IPS from providing those rewrites for nginx? You said many people use it so why not support it if it just takes to come up with some sort of rewrites once? That is if in fact the only thing that's stopping it from working are rewrites.

We have many people who decide to which our product has not been tested with. For example people will use litespeed, nginx, and some even windows server which we dont provide support for at all. But we have to draw the line somewhere and say "this is what we support" I suppose is the answer to the question there. Theoretically there would be nothing stopping us providing support for it, the same as anything else you can name. But these all come at a cost of extra development time, testing, and of course introduction of more bugs. I think you may have taken 'many' out of context there. Many is not the majority. In fact it would be a long long way away from a majority in this instance

Posted
1 hour ago, Maxxius said:

And what prevents IPS from providing those rewrites for nginx? You said many people use it so why not support it if it just takes to come up with some sort of rewrites once? That is if in fact the only thing that's stopping it from working are rewrites.

IPS writes software. They don’t provide support for the underlying services that it runs on.  If someone is not comfortable doing those sorts of things themselves, it is better to consider a hosted version of the software. 

Just because something technically works without going out of their way does not mean they have resources to support it when people need support around it  

Regarding nginx itself… the staff don’t use that as a development platform. That means they don’t know it to the same degree they do their primary environment. If they figure out how to do it, people will expect them to support other things related to it as well. They would also be expected to support it if someone can’t get it to work or it needs to be changed in a future version. It’s never “one and done”. 

Instead they are sticking with what they know. If someone wants to do something else and it works… great. But if you run into problems with it, you’re on your own getting your custom setup working. 

Posted

I just wanted to clarify the NGINX 'issue' (although this would apply to any server/proxy/CDN setup that doesn't pass the required header).

You will need to make sure that the HTTP Authorization header is passed through to PHP. Making that header available will enable Zapier to communicate with your community. You'll also need to do this if you want to use other features that use HTTP authentication such as the REST API.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...