To be clear, you want to negotiate whether to send back RDF or another type of content, correct?
You can read up on how content negotiation works here: http://www.w3.org/TR/cooluris/#implementation but the short version is that you need to inspect the Accept header and see if the browser will accept RDF content. If so, you can send back RDF; if not, you send back whatever content the browser indicates priority to. You can implement this all in code - the only app.yaml configuration needed is to route the incoming request ----------------- -Vinny P Technology & Media Consultant Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com On Thu, Feb 12, 2015 at 8:40 AM, lh <lavdim.hali...@gmail.com> wrote: > > Hi, > > I use GAE to run an application. How can I realize content negotiation to > server application/rdf+xml when it is required with GAE using app.ymal or > .htaccess. As GAE run by default in port 8080 I made an apache redirection > using virtual hosts (ProxyPass) from port 80 to 8080. > > Should I use app.yaml or .htaccess (and in which folder to create > .htaccess, GAE or mysite, I tried both but unsuccessful). > Also checked to some solutions like editing app.yaml using some logic from > this link https://gist.github.com/darktable/873098 ,etc. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CALSvALCV-VehXqgK_wVO4LUr6J6Y9Exggm604XtvGQ5gfc6G7A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
