It's always difficult cascading querystring parameters and handlers to be sure they go to the correct item. Though that isn't your problem here it is worth noting and might help others in the future...
The important thing to note is that the &image= is the last querystring parameter and that there can only be one parameter to the second handlers (getimage.ashx in this example).
will apply the &height=500 to imagegen.ashx, not getimage.ashx. That's just the way it works and isn't specific to ImageGen.
Now to the question of port numbers - you'll need ImageGen Professional for this to work as you're attempting it. While in development on localhost you always have the Professional features enabled and you can just include the domain and port as you've shown above. On a live site you probably aren't going to be using port numbers and so won't need to include either the domain or port, and so the free version should be fine. In both cases you don't have to purchase a key unless you want the benefits ImageGen Professional provides.
Thank you for explaining some details, but I still don't see my solution because, like you said, it doesn't seem that I need Pro features. Correct that I'm not using port #'s in test or production, only local development. I gave localhost:1232 examples, but this img src is actually not working in a test environment http://dev.[domain].com:
You will need ImageGen Professional for this to work. I should have mentioned it at the start... ImageGen assumes the &image= parameter can be mapped to a physical file in the website. Thus, ImageGen is looking for the "ImageServer.ashx?imageID=278" as a filename and isn't going to find it, which is why you get the error.
What you really want is for ImageGen to treat the &image= parameter as a (remote) website that will return an image from a specific URL. This feature is only available in ImageGen Professional and you must specify the full url to the resource including the http:// portion even though it resides on the same server.
File Not Found
ImageGen2.5.2
These all serve the image:
http://localhost:1232/ImageServer.ashx?imageID=278
http://localhost:1232/ImageGen.ashx?image=http://localhost:1232/ImageServer.ashx?imageID=278
http://localhost:1232/ImageGen.ashx?image=http://localhost:1232/ImageServer.ashx%3fimageID=278
These give "File not found: /ImageServer.ashx?imageID=278"
http://localhost:1232/ImageGen.ashx?image=/ImageServer.ashx%3fimageID=278
http://localhost:1232/ImageGen.ashx?image=ImageServer.ashx%3fimageID=278
I cannot leave the domain in because I'm not using Pro version of ImageGen., but seems like it should work fine. Any ideas?
Getting xslt error when trying to 'Edit' my post, so here's my edit:
I am not using 'ImageBaseDir' anywhere, either. So that shouldn't be the problem.
It's always difficult cascading querystring parameters and handlers to be sure they go to the correct item. Though that isn't your problem here it is worth noting and might help others in the future...
This will work:
The important thing to note is that the &image= is the last querystring parameter and that there can only be one parameter to the second handlers (getimage.ashx in this example).
As an example of how tricky it gets,
will apply the &height=500 to imagegen.ashx, not getimage.ashx. That's just the way it works and isn't specific to ImageGen.
doug.
Thank you for explaining some details, but I still don't see my solution because, like you said, it doesn't seem that I need Pro features. Correct that I'm not using port #'s in test or production, only local development. I gave localhost:1232 examples, but this img src is actually not working in a test environment http://dev.[domain].com:
And I have double checked that both handler files are in the root of my site.
Thanks again, Doug
Thanks for the clarification.
You will need ImageGen Professional for this to work. I should have mentioned it at the start... ImageGen assumes the &image= parameter can be mapped to a physical file in the website. Thus, ImageGen is looking for the "ImageServer.ashx?imageID=278" as a filename and isn't going to find it, which is why you get the error.
What you really want is for ImageGen to treat the &image= parameter as a (remote) website that will return an image from a specific URL. This feature is only available in ImageGen Professional and you must specify the full url to the resource including the http:// portion even though it resides on the same server.
cheers,
doug.
is working on a reply...