Alain-Aymerick FRANCOIS

Hi,
Thanks for reply. I’ve integrated your fix iun 1.9.8. Keep me informed if it works correctly with 1.9.8.

Best regards.

Hi,

I don’t understand why http/https is not appending because i use SERVER variables that you’ve communicated to me before to make the test and build url. (ie. $_SERVER[ ‘HTTP_HOST’ ],$_SERVER[ ‘HTTP_X_FORWARDED_PORT’ ], $_SERVER[ ‘HTTP_X_FORWARDED_PROTO’ ]).

So, i’m very sorry but i can’t solve your problem.

If you want to say where the problem come from, you must use error_log function inside code to debug.

In your wp-config.ini :

@ini_set(‘display_errors’,’Off’);
@ini_set(‘log_errors’,’On’);
@ini_set(‘error_log’,’/var/www/your-website/phperrors.log’);

Then insert error_log inside code :

$current_url = $_SERVER[ 'HTTP_HOST' ];
error_log( "after HTTP_HOST " . $current_url);

And so on.

if ( $_SERVER[ 'HTTP_X_FORWARDED_PROTO' ] == 'https' ) {
				$current_url = str_replace( "http", "https", $current_url );
			}
error_log( "after HTTP_X_FORWARDED_PROTO " . $current_url);

`

Best regards.

Hi,

In file classes/wp_cassify_utils.php, replace wp_cassify_get_current_url as below. Make all tests you need. Then, keep me informed and if you’ve not bad behaviour with this code, i can integrate this fix in next release :

public static function wp_cassify_get_current_url( $wp_cassify_default_wordpress_blog_http_port = 80, $wp_cassify_default_wordpress_blog_https_port = 443 ) {

		$current_url = ( @$_SERVER[ 'HTTPS' ] == 'on' ) ? 'https://' : 'http://';

		// If cassified application is hosted behind reverse proxy.
		if ( isset( $_SERVER[ 'HTTP_X_FORWARDED_HOST' ] ) ) {
			$current_url .= $_SERVER[ 'HTTP_X_FORWARDED_HOST' ];
		}
		else {
			$current_url .= $_SERVER[ 'SERVER_NAME' ];
		}

		if( ( $_SERVER[ 'SERVER_PORT' ] != $wp_cassify_default_wordpress_blog_http_port ) &&
			( $_SERVER[ 'SERVER_PORT' ] != $wp_cassify_default_wordpress_blog_https_port ) ) {
			$current_url .= ':' . $_SERVER[ 'SERVER_PORT' ];
		} 

		// Specific use case configuration for WordPress hosted on nginx behind AWS loadbalancer.
		if (
			isset( $_SERVER[ 'HTTP_HOST' ] ) &&
			isset( $_SERVER[ 'HTTP_X_FORWARDED_PORT' ] ) &&
			isset( $_SERVER[ 'HTTP_X_FORWARDED_PROTO' ] ) ) {

			$current_url = $_SERVER[ 'HTTP_HOST' ];

			if( ( $_SERVER[ 'HTTP_X_FORWARDED_PORT' ] != $wp_cassify_default_wordpress_blog_http_port ) &&
				( $_SERVER[ 'HTTP_X_FORWARDED_PORT' ] != $wp_cassify_default_wordpress_blog_https_port ) ) {
				$current_url .= ':' . $_SERVER[ 'SERVER_PORT' ];
			} 	

			if ( $_SERVER[ 'HTTP_X_FORWARDED_PROTO' ] == 'https' ) {
				$current_url = str_replace( "http", "https", $current_url );
			}
		}

		$current_url .= $_SERVER[ 'REQUEST_URI' ];

		return $current_url;
	}

Best regards.

Hi,

I close ticket cause i answered to your question.

Best regards.

Hi !

Have you done the test for http://www.somedomain.com/mockup/test2.php or https://www.somedomain.com/mockup/test2.php ?

I search what’s php server variables i should use to build callback service url if you’re behind a proxy.

I have already experienced this problem and i was thinking i’ve solved this problem but obviously not :
https://wordpress.org/support/topic/error-beyond-a-reverse-proxy?replies=2

Best regards.

Hi,
Okay, thanks for this informations. I know the source of the of the problem. But i need your help to solve the problem because i’ve not aws loadbalancer.

Create test.php behind your loadbalancer with this code below and send me the output :
<? echo print_r( $_SERVER ); ?>

Best regards.

Hi,

This is because WP Cassify can’t parse xml response given by CAS server to extract user id. You can enable debug option in plugin admin panel to analyse last CAS XML response. Then you can understand why it doesn’t work.

Is your CAS server compatible with CAS protocol version 3 ? Have you tried to turn CAS protocol version to 2 ?

Best regards.