<div dir="ltr"><div>Hello all,<br><br></div>I want to add some more info to my issue to help make it easier to debug. I have used the demo application hosted on <a href="http://freeside.biz">freeside.biz</a> located at <a href="http://webdemo.freeside.biz:82/">http://webdemo.freeside.biz:82/</a>, while I can't make calls to the API because of server settings. I should be able to go to this link: <a href="http://webdemo.freeside.biz:82/rt/REST/1.0/ticket/286/show">http://webdemo.freeside.biz:82/rt/REST/1.0/ticket/286/show</a> and get an object populated with that's ticket data. Instead I get a 404 when if the ticket just didn't exist I should be redirected to the home page. I am wondering if there is extra settings you need to configure to allow for RT's REST API to be used. Or maybe that API is blocked by default for freeside integrated builds of RT. If any body knows if either of my theories hold weight let me know. Thank you guys for taking the time to look at this and have a great weekend.<br>
<br>Corey Young.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 3:00 PM, <span dir="ltr"><<a href="mailto:freeside-devel-request@freeside.biz" target="_blank">freeside-devel-request@freeside.biz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send freeside-devel mailing list submissions to<br>
<a href="mailto:freeside-devel@freeside.biz">freeside-devel@freeside.biz</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://freeside.biz/cgi-bin/mailman/listinfo/freeside-devel" target="_blank">http://freeside.biz/cgi-bin/mailman/listinfo/freeside-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:freeside-devel-request@freeside.biz">freeside-devel-request@freeside.biz</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:freeside-devel-owner@freeside.biz">freeside-devel-owner@freeside.biz</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of freeside-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: freeside-devel Digest, Vol 60, Issue 6 (Corey Young)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 23 Jan 2014 10:19:49 -0500<br>
From: Corey Young <<a href="mailto:eric.c.f.young@gmail.com">eric.c.f.young@gmail.com</a>><br>
To: <a href="mailto:freeside-devel@freeside.biz">freeside-devel@freeside.biz</a><br>
Subject: Re: [freeside-devel] freeside-devel Digest, Vol 60, Issue 6<br>
Message-ID:<br>
<<a href="mailto:CAN2a1nD5MKAZts2BO96ZMiM-YWe7sDP0wTTbxxHQpkvLL3fXHw@mail.gmail.com">CAN2a1nD5MKAZts2BO96ZMiM-YWe7sDP0wTTbxxHQpkvLL3fXHw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
That fix has corrected the auth error, but not I am getting a 404. With the<br>
appliance I get [Thu Jan 23 07:05:27 2014] [error] [client 69.196.6.39]<br>
File does not exist: /var/www/freeside/rt/REST/1.0/ticket/1. On a stand<br>
alone installation when you access a REST command that doesn't exist it<br>
just redirects you back to RT. Has anyone ran into an issue like this?<br>
<br>
<br>
On Tue, Jan 21, 2014 at 3:00 PM, <<a href="mailto:freeside-devel-request@freeside.biz">freeside-devel-request@freeside.biz</a>>wrote:<br>
<br>
> Send freeside-devel mailing list submissions to<br>
> <a href="mailto:freeside-devel@freeside.biz">freeside-devel@freeside.biz</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="http://freeside.biz/cgi-bin/mailman/listinfo/freeside-devel" target="_blank">http://freeside.biz/cgi-bin/mailman/listinfo/freeside-devel</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:freeside-devel-request@freeside.biz">freeside-devel-request@freeside.biz</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:freeside-devel-owner@freeside.biz">freeside-devel-owner@freeside.biz</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of freeside-devel digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: Building Self Service Application (Kristian Hoffmann)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Mon, 20 Jan 2014 14:06:15 -0800<br>
> From: Kristian Hoffmann <<a href="mailto:khoff@fire2wire.com">khoff@fire2wire.com</a>><br>
> To: <a href="mailto:freeside-devel@freeside.biz">freeside-devel@freeside.biz</a><br>
> Subject: Re: [freeside-devel] Building Self Service Application<br>
> Message-ID: <<a href="mailto:52DD9DD7.6030000@fire2wire.com">52DD9DD7.6030000@fire2wire.com</a>><br>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
><br>
> On 01/20/2014 08:56 AM, Corey Young wrote:<br>
> > Hello everyone,<br>
> ><br>
> > I am currently building an application to interface with your self<br>
> > service API using PHP. One of the requirements of my project is to<br>
> > access ticket information in RT. The issue I am having is when I try<br>
> > to access the REST api for RT on a freeside implementation I get a 401<br>
> > error which is unauthorized. I have tried on a custom installation as<br>
> > well the demo app supplied. When I use a stand alone RT installation<br>
> > the REST API works properly. I am wondering if there is a<br>
> > configuration option to allow the RT REST API to work within a<br>
> > freeside application. Thank you for taking the time to read and have a<br>
> > great day.<br>
><br>
> You could try something like this in your apache config...<br>
><br>
> <Directory /fs/path/to/RT/REST><br>
><br>
> Satisfy Any<br>
> Allow from all<br>
><br>
> </Directory><br>
><br>
><br>
> -Kristian<br>
><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> freeside-devel mailing list<br>
> <a href="mailto:freeside-devel@freeside.biz">freeside-devel@freeside.biz</a><br>
> <a href="http://freeside.biz/cgi-bin/mailman/listinfo/freeside-devel" target="_blank">http://freeside.biz/cgi-bin/mailman/listinfo/freeside-devel</a><br>
><br>
><br>
> End of freeside-devel Digest, Vol 60, Issue 6<br>
> *********************************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://freeside.biz/pipermail/freeside-devel/attachments/20140123/78180cb3/attachment-0001.html" target="_blank">http://freeside.biz/pipermail/freeside-devel/attachments/20140123/78180cb3/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
freeside-devel mailing list<br>
<a href="mailto:freeside-devel@freeside.biz">freeside-devel@freeside.biz</a><br>
<a href="http://freeside.biz/cgi-bin/mailman/listinfo/freeside-devel" target="_blank">http://freeside.biz/cgi-bin/mailman/listinfo/freeside-devel</a><br>
<br>
<br>
End of freeside-devel Digest, Vol 60, Issue 7<br>
*********************************************<br>
</blockquote></div><br></div>