Thanks for the clarification. I was able to reproduce the problem on my local machine and fix it.
It is now fixed in our source code repository so it will be fixed in the next release of mojoPortal.
The only workaround I can suggest until then is manually change the relative url to a fully qualified url after browsing and save it.
Thanks,
Joe