[ixpmanager] Bug in rendering of the Router screen

[Mike Hammett]

--- 
> What's curious (and the bug) is the lack of CSS when APP_URL points to a 
> site that has a redirect. 

This is not unusual in modern browsers: if the main site is https and it 
tries to pull in non-HTTPS resources, the browser (current Chrome, and 
same for Firefox afaik) won't even make the attempt to pull the resource 
and so will not even see the redirect. 

In other words: normal, expected and safe behaviour enforcement by your 
browser. 

You'll see the fails in developer tools if enabled. 
--- 


Ah, the luxury of modern browsers not only making decisions for you, but not even telling you that it made a decision. I had a similar issue when Cloudflare-enabling my site. 




----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

----- Original Message -----

From: "Barry O'Donovan" <barry.odonovan at inex.ie> 
To: "INEX IXP Manager Mailing List" <ixpmanager at inex.ie> 
Sent: Wednesday, October 18, 2017 1:16:48 AM 
Subject: Re: [ixpmanager] Bug in rendering of the Router screen 

Hi Mark, 

Mark Prior wrote: 
> I've been playing with IXP manager on my Debian system (so I've had to 
> take the manual installation path) 

Cool, should be mostly the same as our default of Ubuntu with some minor 
tweaks. 

The two references for this (for other people reading this email are): 

http://docs.ixpmanager.org/install/manually/ 

and the all-in-one scripts is the best documentation: 

http://docs.ixpmanager.org/install/automated-script/ 

If you want to contribute (and will maintain) a Debian version of this, 
we'd be happy to have it. Just open a PR - see: 

https://github.com/inex/IXP-Manager/blob/master/CONTRIBUTING.md 

NB: if our documentation is /anyway/ lacking, please PLEASE contribute 
back suggestions via: 

http://docs.ixpmanager.org/dev/docs/ 

> Initially I was lazy and hadn't changed the default setting for APP_URL 
> in the .env file and while the other screens worked fine (I could create 
> Customers, Infrastructures, Switches, etc) the Router screen gave the 
> appearance of missing the CSS. 

Right, so that's the difference between the current two two frameworks 
in use (Zend Framework which is being migrated to Laravel). 

The ones that worked were ZF, the ones that didn't were Laravel. 

> Note I don't have a web service listening 
> on port 8088 (which is the default value for APP_URL). 

You must be looking at a different file, the sample config is 
'localhost' via: 

https://github.com/inex/IXP-Manager/blob/master/.env.example 


> I edited the .env file to include the URL for the web site but neglected 
> to change http to https and got the same result, ie missing CSS. Note 
> that there is a redirect in the apache configuration so when you try to 
> display /router/list there is a 302 redirect to the https site (although 
> the initial login redirects you to the https site if there wasn't an 
> absolute URL being used later). 
> 
> I eventually worked out that I was missing the "s" and changed APP_URL 
> appropriately and now I get the raft of CSS and JS files loaded so that 
> the Routers screen renders properly. 

Cool. 

> What's curious (and the bug) is the lack of CSS when APP_URL points to a 
> site that has a redirect. 

This is not unusual in modern browsers: if the main site is https and it 
tries to pull in non-HTTPS resources, the browser (current Chrome, and 
same for Firefox afaik) won't even make the attempt to pull the resource 
and so will not even see the redirect. 

In other words: normal, expected and safe behaviour enforcement by your 
browser. 

You'll see the fails in developer tools if enabled. 

- Barry 


-- 

Kind regards, 
Barry O'Donovan 
INEX Operations 

https://www.inex.ie/support/ 
+353 1 531 3339 


_______________________________________________ 
INEX IXP Manager mailing list 
ixpmanager at inex.ie 
https://www.inex.ie/mailman/listinfo/ixpmanager 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20171018/326ab358/attachment.html>