Re: [Catalyst] Access-Control-Allow-Origin
cOn 15 Jun 2018, at 13:54, Theo Bot wrote:
Can anybody tell me to to add an "Access-Control-Allow-Origin" in the
header:
I've tried "$c->response->header('Access-Control-Allow-Origin' =>
'*');
That's how you do it.
But I don't see it in the response
Is that line of code actually running for the response?
Have you put it on the wrong route by mistake?
Are you putting it on the response for a POST or GET request when the
browser is making a preflight OPTIONS request which isn't being handled
by that?
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] New design
On 23 Jul 2013, at 9:48, Mark Keating wrote: The nice chaps at Evozon have recently been making design mocks for a bunch of Perl sites and they have come up with a fresh look for Catalyst. Take a look and let me know what you guys think. It's very pretty, I *love* the look of many of the graphics, and there are some nice ideas in there. However, it is a very wide design which is going to lead to horizontal scrolling (the red section could do with having 2 rows of 3 things instead of 1 of 5, the space between the text and the book graphic could be reduced, the two guides to getting a decent Perl environment could do with being shunted off to their own page with a choice of links instead of a choice of columns) with some very tiny fonts (really tiny, the font size could do with being a lot bigger). I like the space theme, although as other people have commented it isn't Catalyst's traditional theme. I'd carry the dotted graphic theme through to the red section though (possibly with the telescope being done in that style). The Dancing astronauts are cute but more suggestive of Dancer than Catalyst! Then we come to Man With A Brick. Putting the first brick in place is a good image for getting started … but completely breaks from the space theme from elsewhere in the page. It's also the first section that uses translucent backgrounds and it really feels like part of a different site. The list of clients is nice, very clear and good at highlighting some high profile users of Catalyst. It suffers from too-many-columns but that is easily fixed. -- David Dorward http://dorward.co.uk/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] List of Applications using Catalyst
On 10 Jun 2013, at 15:50, John Napiorkowski wrote: As for the former, there's not a lot of people actively maintaining the site. I couldn't find anywhere on the site that invites people to join in with the maintenance. It could do with an obvious sign up page (even if it comes with a you must have your account approved by an admin proviso to combat spam). -- David Dorward http://dorward.co.uk/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Slash character in argument of request URL
On 8 Apr 2013, at 13:06, Kieren Diment dim...@gmail.com wrote: Slashes in urls that aren't path separators are a pain. Avoid by adjusting your implementation. +1 I once had to write a CGI script to use as a 404 handler to deal with Apache not liking %2F. (I believe at that stage we could have also solved the problem by not using an out of date Apache, but on high rejected that option). -- David Dorward http://dorward.co.uk ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Creating HTML docs from POD
On 30 Oct 2010, at 15:29, Octavian Rasnita wrote: Is there a tool that can be used to extract the POD from all the modules of a Catalyst app and create an HTML version of that documentation? http://search.cpan.org/search?query=pod%20htmlmode=all -- David Dorward http://dorward.me.uk ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] How to detect if the current form request is a post?
kakim...@tpg.com.au wrote: Read my response. I said 1) POST is the prefered method Not according to the standard. Everything has its place. 2) using GET for a content sensitive site like an online banking site is bad. I m sure you would not want to have people book marking your session ID , or worst, the user credentials used to login and access certain pages which are private to the authorised user. The session id shouldn't be in the URI, that's what cookies are for. Authentication credentials are an exception to the normal guideline. But everything else? Why shouldn't I bookmark the latest transactions page of my credit card account? Or the Give me a form so I can pay my electricity bill page? -- David Dorward ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] How to detect if the current form request is a post?
kakim...@tpg.com.au wrote: -- So, tell me, would you like to allow people to bookmark transaction ID numbers or attributes which are not permanent (ie will last until a transaction is done)? Why would a user try to bookmark such a page? It doesn't make sense. What harm would it do if they did anyway? At worst, they should get an Unrecognized transaction error. More usefully, a log of the transaction could be supplied. Fact is, guidelines are there for best practices but rules are meant to be bent when we encounter different problems/scenarios. Another factor is the business rules. If they business doesn't want its subscribers (for what ever business acumen/reason Such as? or perhaps to discount future maintenance of having to put in redirects when they decommission or rename certain URIs) to have a bookmark for them to achieve certain things (ie. look at their electricity bills), then POST would be the better pick. Limiting the side effects of laziness and bad practices with other bad practices ... well, that's an interesting argument, I'll give you that. Also, when POST is used , the URL on the url address bar of the browser remains clean without the extra params. URLs should be designed to be useful, not pretty (with the possible exception of those to be printed out on promotional materials - which the ones under discussion wouldn't be). -- David Dorward http://dorward.me.uk/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst - any good AJAX tutes?
kakim...@tpg.com.au wrote: I would like to use AJAX in my catalyst app. Any good references/tutes to recommend? Ajax just comes down to making HTTP requests without leaving the page using JavaScript. There isn't really anything Catalyst specific about it (except possibly a mention that Catalyst::View::JSON could be useful for presenting data in a way that is easy to parse using JavaScript). For some general Ajax material I would suggest http://domscripting.com/blog/display/41 and a library such as http://developer.yahoo.com/yui/connection/ -- David Dorward http://dorward.me.uk/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
