• February 24, 2025, 01:08:00 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 [2]

Author Topic: HTTPS dont work??  (Read 14543 times)

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: HTTPS dont work??
« Reply #15 on: February 18, 2010, 04:49:35 PM »

I am sorry you don't like the PDFs, I wish you the best of luck in the future.

Also while discussing configuration resources the FAQs on http://support.dlink.com tend to be a little easier to follow if the PDFs are a little too abstract or not verbose enough for you.

If you are having the opposite problem and need to know the technical aspects of ANY given command the manual and CLI manual are VERY VERY specific.  This is why they would use a solid ream of paper if printed (I know I have a copy of them that was printed).

If we still aren't addressing your documentation needs then drop a line in the thread stickied at the top of this board asking for documentation requests.  The people who write the FAQs for this product do check that board, though given the complete lack of interest from customers, they may give it up.

As for this specific issue, the problem tends to be that people don't consider rule order, which is why my script made the HTTP ALG rule the first one.
Logged
non progredi est regredi

gracoat

  • Level 1 Member
  • *
  • Posts: 2
Re: HTTPS dont work??
« Reply #16 on: April 21, 2010, 10:57:47 AM »

I'm exactly one step past this post.  The filter works perfectly with this setup.  However, if you type https://www.facebook.com it allows access to the site because the http_new only specifies port 80.  If you include port 443 in there, all secure sites become blocked.  Everything.  If it has an https prefix to the address, the page will not load.

Any ideas?
Logged

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: HTTPS dont work??
« Reply #17 on: April 21, 2010, 01:56:29 PM »

I just posted a response to your issue in another thread.  In the future, try to keep your issue on a single thread for ease of management and following your particular issue.
Logged
non progredi est regredi
Pages: 1 [2]