When purchasing Performance licenses, the ImageResizer website states that it comes with "1 wildcard domain".
I was under the impression that Performance licenses apply to multiple domains, if those domains are simply aliases for the same website?
In this case, the different domains are used to separate different language versions of a website:
tempuri.com -> English website
tempuri.se -> Swedish website
This is instead of using a common domain and URL prefixes, something like:
tempuri.com/en -> English
tempuri.com/se -> Swedish
In the first case, would we need 1 license per domain?
Also, if the domains aren't exactly the same (depending on domain availability) like...
tempuri.com -> English
tempuri-sweden.se -> Swedish
tempuri-denmark.dk -> Danish
...would we then require 3 licenses to support the three languages?
Thanks!
Performance licenses include exactly 1 domain; they are tied to the HTTP HOST header that ImageResizer receives. While subdomains are included, unrelated domains are not. All documentation is very clear on this point - it is a domain license, not a site or website or server license. http://imageresizing.net/plugins/editions/performance
ImageResizer Elite licenses are DRM-free and can be used on an unlimited number of domains.
Related
I know this question has been asked before, but I want to know if there is a better more efficient way to block both the Russian Federation and Ukraine Countries from accessing my websites.
These countries are constantly ripping my website, using massive amounts of bandwidth, and and also providing BS porn related refer URLs to the sites. BTW... the Chinese are no better.
The following website provides a list if IP address for these countries so you can add them to the deny from ###.###.###.### in the .htaccess file.
The problem is that both the Russian Federation list has over 11,000 IP addresses and the Ukraine list has over 4,000 IP addresses.
This would mean adding about 15,000 deny from ###.###.###.### lines to the .htaccess file.
Questions:
(1) Would adding this many deny statements be inefficient, thus adding too much overhead to the Apache server because every hit would have to be looked up in the deny list?
(2) Is there a better more efficient way to do this?
BTW... a few of my important websites are built on the Drupal 6.x CMS system.
Note: My websites are hosted on a shared server. Therefore I do not have access to the root or Apache system.
Thanks in advance.
My client owns "domain.com". We need to give various applications friendly names for internal and external access. The applications are WCF web services and MVC web applications with varying levels of authentication (Windows auth within and across AD domains and plain text authentication). It looks a little like this:
UAT Environment
service1.uat.services.domain.com
service2.uat.services.domain.com
service3.uat.services.domain.com
service4.uat.services.domain.com
application1.uat.apps.domain.com
application2.uat.apps.domain.com
Production Environment
service1.services.domain.com
service2.services.domain.com
service3.services.domain.com
service4.services.domain.com
application1.apps.domain.com
application2.apps.domain.com
We're likely to have a LOT more sub domains, and everything needs to be secured with SSL.
We've changed our minds on how to configure this a number of times, but now we've hit a possible restriction. We thought a wildcard SSL certificate might work, but apparently they only work to a single level of subdomain i.e. *.services.domain.com.
Because of budget, we'd like to register a single wildcard SSL certificate and apply it to multiple servers (belonging to multiple AD Domains, and also a few servers in our DMZ).
This morning I had an idea, but I don't know enough about this stuff to make a definite decision. Do any of you foresee any restrictions on using the following naming convention instead of the above?
service1-uat-services.domain.com
service2-uat-services.domain.com
service3-uat-services.domain.com
service4-uat-services.domain.com
application1-uat-apps.domain.com
application2-uat-apps.domain.com
service1-services.domain.com
service2-services.domain.com
service3-services.domain.com
service4-services.domain.com
application1-apps.domain.com
application2-apps.domain.com
That way, we can register a wildcard for *.domain.com and use a single level subdomain for each application / service, but still allow us to keep everything logically separate. Are there any technical issues anyone can identify using this set up?
There shouldn't be any problem with that.
I have read about everything about this situation and had very different recommendations and read many differents scenarios from 2007 to 2010. But nothing exactly like my case even here on stackoverflow, so I'm here to ask the real experts. Considering this:
website1.com
- hosting: simplehelix
- domain name: simplehelix
- main magento installation (1.3.2.4)
- SSL installed
- paypal PRO (credit card taken directly on this site)
website2.com
- hosting: none
- domain name: goddady
- DNS/nameserver: to simplehelix servers
- folder called /website2/ that loads magento
- paypal PRO (credit card taken directly on this site)
website3.com
- hosting: geohost
- domain name: geohost
- DNS/nameserver: to simplehelix servers
- folder called /website3/ that loads magento
- paypal PRO (credit card taken directly on this site)
All 3 sites share most of the same products (80%) because they are 3 real physical businesses from the same owner having mostly the same products. They use one Magento admin for products, categories, customers, sales.
QUESTION: Now, in 2011, I'd like to know exactly what is the simplest, easiest, fastest way to have SSL on website2 and website3 so that all our transactions are secured? Can I just buy SSL on godaddy and geohost and install it there on the domain names and it will work even if the DNS is pointing to simplehelix? Do i have to reinstall magento on 2 new hosting plans + ssl and not be able to share same database?
Note:
- we do not want to share carts
- we want people to stay on the respective websites
- we want to use paypal pro
- keep cost down
- please be clear on your steps/description, as this might help many other people more/less technical
Thank you for your help
Joel
I'm not sure how you've had different recommendations. The answer is simple: you'll need to buy an SSL certificate for each of your domains that you want secured.
Sharing a Magento installation, talking about the DNS, etc, is not relevant.
Buy the SSL certificates, get your webhost (it looks like you're using SimpleHelix for hosting all of the websites) to install them all for you, then change the secure URL in the Magento admin for each of your stores (use the dropdown in the configuration area to change the configuration scope from Global to each store in turn) to the appropriate URL, presumably https://www.website{1,2,3}.com from http://www.website{1,2,3}.com.
Easy :)
Sounds like you need to think of Magento terminology 'stores' or 'websites' - with 'stores' you can have lots of them on the same SSL, sharing the same checkout. However, if you have built your sites with 'websites' then you cannot have them all go to the same checkout and you will need multiple IP addresses.
It is relatively simple to move your hosting to a VPS that supports more than one IP address, although check before you leap. It is also possible to move your 'stores' to a single 'website' in Magento.
Ok, it seems that the easiest way to do this was to buy 2 new hosting accounts at my hosting provider and then buy SSL on both and ask them to redirect to the Magento installation. It worked, but it cost 2x hosting account that I do not use at all...
Right now there's two different accounts, with both domains having each their own hosting account,
for similar website (let's say domain.fr and domain.co.uk)!
I've merged the two websites into one (currently hosted as 0.0.0.0/site/language ),
making it multilanguage! The script just need a prefix on root,
such as like www.domain.com/english/ or www.domain.com/french.
This works as expected, if only a domain is used, but I would like to use two different domains (domain.fr / domain.co.uk).
So, I want to catch the current request URL, to know what language to display. What's important is that, the request urls keep persistent.
For example,
http://domain.co.uk/language_english
http://domain.co.uk/language_english/somepage.php
http://domain.co.uk/language_english/somedirectory/someotherpage.php
While,
http://domain.fr/language_french
http://domain.fr/language_french/somepage.php
http://domain.fr/language_french/somedirectory/someotherpage.php
This two domains are actuall hosted in same hosting account, let's said
127.0.0.1/language_variable/somepage.php
Any suggestions or good practices?
If I got your question , It's a feature in Web Hosting's solution which is called Addon Domains and depend on hosting company that how many Addon Domain they let you to put into one account !
37signals is a web app company. Some of their applications:
basecamp, to manage projects
highrise, to manage contacts
backpack, like a wiki
they use different domains for each application (basecamphq.com, highrisehq.com, etc)
in basecamp, this is the address of a particular comment for a post in a project of my company (acme) https://acme.basecamphq.com/projects/431678/posts/2964581/comments#5854236
if 37signals had chosen to host all the applications under their domain using folders (eg 37signals.com/basecamp/..., how would you design the paths RESTfully?
Um, how about something like
http://www.37signals.com/[PRODUCTNAME]/projects/431678/posts/2964581/comments#5854236
Not quite sure what you're asking, really.