[thelist] eCommerce / Secure Cert / domain path question

[John List]

On 07/17/2010 02:19 PM, Brian White - WebHostingSolutions.com wrote:
> At 11:00 AM -0700 7/17/10, Bill Moseley wrote:
>> On Sat, Jul 17, 2010 at 10:52 AM, Brian White - 
>> WebHostingSolutions.com <
>> bwhite at webhostingsolutions.com> wrote:
>>
>>>  A client has website abc; wishes to add abc/some_other_service and 
>>> perhaps
>>>>  abc/some_otherservice2
>>>>
>>>>  www.abc.com
>>>>  www.abc/some_otherservice1
>>>>  www.abc/some_otherservice2
>>>>
>>>>  If the secure certificate was purchased for abc.com, then yes, 
>>>> anything
>>>  under/trailing abc.com can be secure, as long as the links begin with
>>>  https and of course include abc.com as the qualified domain in the 
>>> URL.
>>>
>>
>> To be clear, cert for abc.com works for https:://abc.com, not for
>> https://www.abc.com/.  And a wildcard cert for *.abc.com does not 
>> work for
>> http://abc.com/ (but *.abc.com works).  And cert for www.abc.com only 
>> works
>> for https://www.abc.com, not https://abc.com.
>>
>> Pick your poison.
>> Bill Moseley
>> moseley at hank.org
>
> You can get a secure cert that will work for *both* www and without 
> www (that's what we do).
>
> Regards,

I wasn't aware of a single cert that works for both (other than a wild 
card cert, which is usually outlandishly expensive). Where do you get yours?

Thanks,
John