Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mod to base url structure #1232

Merged
merged 3 commits into from Nov 18, 2017
Merged

Conversation

sjpadgett
Copy link
Sponsor Member

@sjpadgett sjpadgett commented Nov 17, 2017

Trying to live in Docker and AWS world. @bradymiller Think you could get this on demo site or my up for grab? I can use relative pathing to a point for my rest api calls but depending where my call originates, I may need base path, especially if sharing same controller between two app's(Openemr and portal). Proxies, Redirects and load balancer's tend to leave a trail and hoping it is with HTTP_X_FORWARDED_PROTO and if not I put a flag in Globals to force proper protocol....

(below added by bradymiller)
Demo: http://www.open-emr.org/wiki/index.php/Development_Demo#Epsilon_-_Up_For_Grabs_Demo

@bradymiller
Copy link
Sponsor Member

Just set up a Up For Grabs demo for this at:
http://www.open-emr.org/wiki/index.php/Development_Demo#Epsilon_-_Up_For_Grabs_Demo

@sjpadgett
Copy link
Sponsor Member Author

@bradymiller Forcing protocol works as I expected. Not too worried I have to do this for Docker Demo's and I suggest you setup a rewrite rule for the ngnix or set the forwarded super somehow but, I am a little concerned with the AWS install whether that environment carries along the https protocol supers. I'm pretty sure it needs to be handled because of the load balancing or proxies. I think the acceptable solution for indicating SSL via redirects is using/setting the $_SERVER['HTTP_X_FORWARDED_PROTO']( I don't mind being educated here ).
How I handle my REST api calls is not unusual or is it unusual to rely on supers to set up a base url for said calls i.e. one simply can't completely rely only using relative uri's. Maybe @MatthewVita can shed some light on how his AWS installs handle this dilemma and if Carecoordination and portals have been tested on AWS...

@bradymiller
Copy link
Sponsor Member

@sjpadgett , I gotta read up on this. Sounds like you at least got it working on the demo farm with the https force. I'll research the HTTP_X_FORWARDED_PROTO stuff.

@bradymiller bradymiller self-assigned this Nov 17, 2017
@bradymiller bradymiller added this to the 5.0.1 milestone Nov 17, 2017
@sjpadgett
Copy link
Sponsor Member Author

sjpadgett commented Nov 17, 2017 via email

@sjpadgett
Copy link
Sponsor Member Author

@bradymiller I don't know why I didn't think of sooner but I'll just handle my url builder same way I did for the calendar classes and exclude the protocol..duh. Surprise you didn't catch me on that. So Doctor, is there a pill for senility? Thank goodness you're a patient man...

@sjpadgett
Copy link
Sponsor Member Author

@bradymiller Fingers crossed this will work with Docker thus should be okay for AWS. Reset my up for grab and I can test both eye and this.

@bradymiller
Copy link
Sponsor Member

bradymiller commented Nov 18, 2017

Demo has been restarted.
(btw, should be able to get the eye PR demo up soon when get home)

@sjpadgett
Copy link
Sponsor Member Author

@bradymiller Finally, Looks like we're good to go. Once again, thank you for the help and patience...

@bradymiller
Copy link
Sponsor Member

Great! Do we still need the global?

@sjpadgett
Copy link
Sponsor Member Author

sjpadgett commented Nov 18, 2017 via email

@bradymiller bradymiller merged commit 181b1ad into openemr:master Nov 18, 2017
@bradymiller
Copy link
Sponsor Member

Just brought it in. Thanks for the fix! -brady

@sjpadgett sjpadgett deleted the portal-mixed-content branch June 9, 2018 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants