Topic: Certificate Error...

[MeasureUp]

Recently I notice that a warning message pups up when I switch to the swamp home page. (see the image attached)
I have never had this before.
Do you know what is wrong? Thanks for your help.

[JohnK]

We moved to a different server.

Also this post is in the autolisp forum and is subject to movement to a more appropriate forum.

[MeasureUp]

Thanks but how can I get rid of it?

[MickD]

Thanks but how can I get rid of it?

I don't use IE/Edge but you can click on the more information drop down section and there should be a way to accept the certificate (it creates and Exception for this site and adds it to the 'safe' list)

[MP]

Replace https:// with http://

[JohnK]

Thanks but how can I get rid of it?

I don't use IE/Edge but you can click on the more information drop down section and there should be a way to accept the certificate (it creates and Exception for this site and adds it to the 'safe' list)

What he said.

[MeasureUp]

Thanks to MP. "http" works as a charm.

To Mick.
I have no choice. I use company's pc. IE is the only browser allowed to use.
And it seems there is nothing I can do as IT disables the add function to add it to "Certification Authorities store".
BTW Here is subtracted from the drop down section.

•If you arrived at this page by clicking a link, check the website address in the address bar to be sure that it is the address you were expecting.
•When going to a website with an address such as https://example.com, try adding the 'www' to the address, https://www.example.com.
For more information, see "Certificate Errors" in Internet Explorer Help.

Thanks but how can I get rid of it?

I don't use IE/Edge but you can click on the more information drop down section and there should be a way to accept the certificate (it creates and Exception for this site and adds it to the 'safe' list)

Thanks again for everyone's help.

[MickD]

To Mick.
I have no choice. I use company's pc. IE is the only browser allowed to use.

When will they ever learn...?

[MeasureUp]

One day IT detected that staff use Firefox/Chrome portables. Then IT sent warning message to everyone to remove them from machines.
- IT has also disabled the install function on all machines in the company, preventing anyone to install programs.

[MP]

Thanks MP.

You’re welcome. Sorry to hear you have a draconian IT group. It’s unfortunate when the tail wags the dog.

[ronjonp]

To Mick.
I have no choice. I use company's pc. IE is the only browser allowed to use.

When will they ever learn...?

Yikes! Who forces people to use IE?!! You guys still running XP too? 

[dgorsman]

We're required to use IE, but not restricted from using Chrome (for example).  Some of our internal sites and a few external portals only function properly on IE.

Also, Chrome doesn't support rendering XML as HTML using an XSL stylesheet; apparently it's a "security feature" (read as: "we just don't want to do it") which is highly useful for self-documenting data files.

And no, we're not on XP.   

[MeasureUp]

I was suspecting that IT has added swamp's address to their block list so I started the thread.

When will they ever learn...?

Yikes! Who forces people to use IE?!! You guys still running XP too? 

Who forces...
The answer is always "IT". 

BTW We use Win7.

[ronjonp]

I was suspecting that IT has added swamp's address to their block list so I started the thread.

When will they ever learn...?

Yikes! Who forces people to use IE?!! You guys still running XP too? 

Who forces...
The answer is always "IT". 

BTW We use Win7.

Glad I'm "IT"    .. you're a bit behind the times with your OS too.

[Atook]

...Also, Chrome doesn't support rendering XML as HTML using an XSL stylesheet; apparently it's a "security feature" (read as: "we just don't want to do it") which is highly useful for self-documenting data files....

There's a good reason not to support that for local files..

Imagine this scenario:

    You receive an email message from an attacker containing a web page as an attachment, which you download.

    You open the now-local web page in your browser.

    The local web page creates an <iframe> whose source is https://mail.google.com/mail/.

    Because you are logged in to Gmail, the frame loads the messages in your inbox.

    The local web page reads the contents of the frame by using JavaScript to access frames[0].document.documentElement.innerHTML. (An online web page would not be able to perform this step because it would come from a non-Gmail origin; the same-origin policy would cause the read to fail.)

    The local web page places the contents of your inbox into a <textarea> and submits the data via a form POST to the attacker's web server. Now the attacker has your inbox, which may be useful for spamming or identify theft.

Chrome foils the above scenario by putting restrictions on local files opened using Chrome. To overcome these restrictions, you've got two solutions:

    Try running Chrome with the --allow-file-access-from-files flag. I've not tested this myself, but if it works, your system will now also be vulnerable to scenarios of the kind mentioned above.

    Upload it to a host, and problem solved.