<stellar-slack>
<sacarlson> I'm working on integrating federation into my Stellar Wallet but I have run into a problem with Access-Control-Allow-Origin problems were I need to add this header to be sent from your federation server that I'm now running https://github.com/stellar/federation
<stellar-slack>
<sacarlson> otherwise I'll just write another one
de_henne has joined #stellar-dev
stellar-slack1 has joined #stellar-dev
stellar-slack has quit [Ping timeout: 255 seconds]
<stellar-slack1>
<dzham> `Access-Control-Allow-Headers` usually helps too
<stellar-slack1>
<sacarlson> ok well how can I turn it on in this federation app?
<stellar-slack1>
<sacarlson> I seem to have found a solution to my own problem above by adding this line that is hardcoded in the go program : w.Header().Add("Access-Control-Allow-Origin", "*")
<stellar-slack1>
<sacarlson> @eno I'm having the same problem with your federation when used from a browser: XMLHttpRequest cannot load http://256kw.com/federation?q=kiss*256kw.com&type=name. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://zipperhead.ddns.net' is therefore not allowed access.
<stellar-slack1>
<sacarlson> you will need to add the header to allow it to work with a browser that are looking from sites that are not of the same origin
<stellar-slack1>
<sacarlson> otherwise some kind of proxy method or other would be required
<stellar-slack1>
<sacarlson> I've gone ahead and published my updated version of: http://sacarlson.github.io/transaction_tools.html that now has federation support but the only known working address I know is: mailto:sacarlson@zipperhead.ddns.net|sacarlson@zipperhead.ddns.net:8000 due to above problems with server side of federation.
<stellar-slack1>
<sacarlson> so @eno is there a public list of those that now have there public Stellar accounts listed on your domain? If not I was thinking of making one one of mine. I also plan to make a default domain to start search when * or @ is seen at the end to speed entry.
<stellar-slack1>
<dzham> if people just set their home_domain, then it would be an easy thing to do
<stellar-slack1>
<sacarlson> very good idea dzham
<stellar-slack1>
<sacarlson> but I will have to add that
<stellar-slack1>
<sacarlson> so what would we expect in the home domain? I guess something like sacarlson*http://256kw.com|256kw.com ?
<stellar-slack1>
<sacarlson> does horizon already support seaches in home_domain?
<stellar-slack1>
<sacarlson> oh IC so that would be for reverse lookup
<stellar-slack1>
<dzham> yeah
<stellar-slack1>
<sacarlson> but still don't know how I can use that to speed entry without having to type out the whole address
<stellar-slack1>
<dzham> it’s just for reverse lookups
<stellar-slack1>
<sacarlson> I want like google has as you type is fills in what it thinks it is
<stellar-slack1>
<dzham> .. which is why you use federated addresses :)
<stellar-slack1>
<dzham> or QR codes, or whatever
<stellar-slack1>
<sacarlson> oh your looking at it from the oposite side of entering the long type address and get verified that it to the name you hoped it to be.
<stellar-slack1>
<sacarlson> I have no support for that yet
<stellar-slack1>
<sacarlson> I'll add that tomaro
<stellar-slack1>
<sacarlson> I looked at the federated address as a shorter way to manually enter an address without actually entering the long random number
<stellar-slack1>
<jed> Cool eno
<stellar-slack1>
<jed> You need to put your stellar.toml at /.well-known/stellar.toml though
<stellar-slack1>
<dzham> anyone gotten StellarSdk.server.paths() working? it doesn’t generate any requests for me, and all then-callbacks on it fail
pixelb has quit [Ping timeout: 272 seconds]
<stellar-slack1>
<dzham> nvm, my bad
tectonic has joined #stellar-dev
<stellar-slack1>
<sacarlson> I was going to start reverse federation but note that I don't see the home_domain in account info from horizon. is there not a method to get that from horizon?