Ticket #502 (closed Bug report: fixed)

Opened 22 months ago

Last modified 11 months ago

PATCH: Error using ssl and non standard port 443

Reported by: v_w_us@… Owned by: gbastien
Priority: blocker Milestone: Not yet assigned to a Milestone
Component: Auth server, Feature request Version:
Keywords: Cc:

Description

If you configure the auth manager to use SSL but the port is not 443, it does'nt works.

A possible solution:

% diff -c path_defines_url_content.php.orig path_defines_url_content.php *** path_defines_url_content.php.orig 2008-10-29 12:54:38.000000000 +0100 --- path_defines_url_content.php 2008-10-29 12:49:37.000000000 +0100 *************** *** 108,114 ****

/**

  • Define base web address to use (this time using SLL) */

! define('BASE_SSL_PATH', ' https://'.$_SERVER['SERVER_NAME'].SYSTEM_PATH);

} else {

/**

--- 108,120 ----

/**

  • Define base web address to use (this time using SLL) */

! // Non Standard SSL port ! // define('BASE_SSL_PATH', ' https://'.$_SERVER['SERVER_NAME'].SYSTEM_PATH); ! if ($_SERVERSERVER_PORT? != 80 && $_SERVERSERVER_PORT? != 443) { ! define('BASE_SSL_PATH', ' https://'.$_SERVER['SERVER_NAME'] . ':'.$_SERVERSERVER_PORT?. SYSTEM_PATH); ! } else { ! define('BASE_SSL_PATH', ' https://'.$_SERVER['SERVER_NAME'] . SYSTEM_PATH); ! }

} else {

/**

I hope you can set the patch for next version.

Regards

Attachments

Change History

Changed 14 months ago by anonymous

l

Changed 12 months ago by gbastien

  • owner set to gbastien
  • status changed from new to assigned
  • component changed from Auth server, Code Refactoring to Auth server, Feature request
  • summary changed from Error using ssl and non standard port 443 to PATCH: Error using ssl and non standard port 443

Changed 12 months ago by gbastien

  • status changed from assigned to closed
  • resolution set to fixed

Implemented the proposed patch BUT

this fix works only if all gateways have config value SSLAvailable Yes, or else the server determines that even though the connection originated from HTTP by those gateways, it should use SSL and in this case, the port is not right.

Total fix would be to add a way to specify port in Wifidog Virtual Hosts or get the apache port

Changed 11 months ago by benoitg

You have a property in the Virtual Host to tell the auth server if SSL is available. It's necessary for the right links to be generated anyway, might as well use it.

Add/Change #502 (PATCH: Error using ssl and non standard port 443)

Author


E-mail address and user name can be saved in the Preferences.


Action
as closed
The resolution will be deleted. Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.