SOAP::Lite implements the server part through https://metacpan.org/pod/distribution/SOAP-Lite/lib/SOAP/Transport.pod#SOAP::Transport::HTTP and https://metacpan.org/pod/distribution/SOAP-Lite/lib/SOAP/Transport.pod#SOAP::Transport::HTTP::Server.

From reading the documentation, you can either replace the server class by your own server or monkeypatch the ->response method to modify the response when it gets stored.

use SOAP::Transport::HTTP my $old_response = \&SOAP::Transport::HTTP::Server::response; *SOAP::Transport::HTTP::Server::response = sub { my $resp = $old_response->( @_ ); $resp->headers->header('Access-Control-Allow-Origin' => '*'); # is + this wise?! return $resp; };

In reply to Re: CORS header in XMLRPC::Transport::HTTP::Daemon by Corion
in thread CORS header in XMLRPC::Transport::HTTP::Daemon by seaver

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.