basic difference between 8443 and 443

Question

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

parthi-1705 SSCrazy Eights Points: 9277 More actions · Answer 1

433--Could not find CHECK constraint for '%.*ls', although the table is flagged as having one.

8433--The message body may not be NULL. A zero-length UNICODE or binary string is allowed.

Thanks
Parthi

luckysql.kinda SSCertifiable Points: 7816 More actions · Answer 2

433--Could not find CHECK constraint for '%.*ls', although the table is flagged as having one.

8433--The message body may not be NULL. A zero-length UNICODE or binary string is allowed.

where did you get these errors? 8433 is to avoid NULL values whereas 433 is mainly for constraints.

forsqlserver SSCoach Points: 18902 More actions · Answer 3

SSCoach

Points: 18902

December 3, 2009 at 1:49 am

Dear Parthi and Kinda Port is 8443 not 8433

Thanks

luckysql.kinda SSCertifiable Points: 7816 More actions · Answer 4

SSCertifiable

Points: 7816

December 3, 2009 at 2:01 am

Sorry Gupta. I found your question confusing... still

adityaagrawal006 SSC Journeyman Points: 81 More actions · Answer 5

Dear All,

8443 is an alternative for 443.

443 is a secure port for https. Not much difference between the two.

8443 can be used as a port for httpsCA(https with Client Authentication)

Regards,

Aditya