Can we have two services with the same name? Or do these have to be unique? I would say yes, just after some confirmation. Basically and currently only the second one works and fetches the remote image
Can you have a same white listed domain in each of the services
Example: if site A were reachable as http://site-a.com and https://site-a.com
Less of an issue as for most domains, one does redirect to another, but let's assume it's not the case.
Do we need to specify at least one imageprocessor querystring parameter? Currently fetching a rackcdn.com image with ?width=200, but if we omit these settings, nothing happens (error at the iis level)
Any advice on any of the topics is appreciated big time and could involve beer reward (or any other beverage you prefer)
Example: if site A were reachable as http://site-a.com and https://site-a.com Less of an issue as for most domains, one does redirect to another, but let's assume it's not the case.
Really? You should be able to use the one remote service to do both requests since http requests will redirect to https anyway. I've never seen a site that doesn't redirect.
If you needed to use more than one you would have to create a service that inherits the remote one since only one of each type can be registered.
I have to go the double services route, as we'll have non https endpoints as well, think my confusion about http vs https is from the fact I couldn't get 2 services to work. I'll give your suggestion a go and provide feedback!
Already thanks for taking the time to provide some more input!
We got it working based on your feedback, so many thanks for that!
Upgrades > yes, we'll do, guessing it's part of v7.6 (which we want to upgrade to shortly), and if not, we'll update before final release of the website for sure (still some time left before we're there)
So far, so good, we've got one more issue related to proxy and firewall (setup is really a black box to us), but trying to figure that one out before we start bugging the author again ;-)
Having multiple services in security.config, only one RemoteImageService is working fine
hi,
could do with some extra help getting imageprocessor to process remote images from both http and https endpoints.
Current config so far:
Some questions re: current config setup
Can we have two services with the same name? Or do these have to be unique? I would say yes, just after some confirmation. Basically and currently only the second one works and fetches the remote image
Can you have a same white listed domain in each of the services
Example: if site A were reachable as http://site-a.com and https://site-a.com Less of an issue as for most domains, one does redirect to another, but let's assume it's not the case.
Any advice on any of the topics is appreciated big time and could involve beer reward (or any other beverage you prefer)
--Dirk
Also,
Anyone have had ImageProcessor remote image processing working behind a proxy?
--Dirk
Some more info... if we switch both RemoteImageService sections, it seems the last one wins!
Hi Dirk,
Really? You should be able to use the one remote service to do both requests since http requests will redirect to https anyway. I've never seen a site that doesn't redirect.
If you needed to use more than one you would have to create a service that inherits the remote one since only one of each type can be registered.
Btw what version are you using? You never say.
Cheers
James
Hi James,
Good remark about version, I force my team mates to always mention as much info as possible, now I'm forgetting it myself :( #slapintheface^2
We're on
umb v7.5.4
I have to go the double services route, as we'll have non https endpoints as well, think my confusion about http vs https is from the fact I couldn't get 2 services to work. I'll give your suggestion a go and provide feedback!
Already thanks for taking the time to provide some more input!
Beer's on the way ;-)
Hey Dirk,
No worries. :) Best of luck and let me know how you get on.
Cheers
James
P.S bump those versions. Much improved perf in latest ones.
Hi James,
We got it working based on your feedback, so many thanks for that!
Upgrades > yes, we'll do, guessing it's part of v7.6 (which we want to upgrade to shortly), and if not, we'll update before final release of the website for sure (still some time left before we're there)
So far, so good, we've got one more issue related to proxy and firewall (setup is really a black box to us), but trying to figure that one out before we start bugging the author again ;-)
Thanks!
--Dirk
is working on a reply...