Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running not on /, notifications don't arrive #27

Open
onli opened this issue May 21, 2015 · 1 comment
Open

Running not on /, notifications don't arrive #27

onli opened this issue May 21, 2015 · 1 comment

Comments

@onli
Copy link

onli commented May 21, 2015

rack-superfeedr was running fine for some time. But I changed the server, and it is running not under '/' anymore, but under '/feedtragon'. My config.ru looks like this:

require 'rubygems'
require 'bundler'

Bundler.require

require './server.rb'

run Rack::URLMap.new(
'/feedtragon' => Sinatra::Application
)

That is behind an .htaccess that maps /feedtragon to this sinatra app:

RewriteEngine on
RewriteCond %{REQUEST_URI} ^/feedtragon/.*    
RewriteRule (.*) http://localhost:58080/$1 [P]

Now, I already did some changes to restore the subscribe and unsubscribe function, setting base_path via sinatras url-helper: onli/feedtragon@d538a33

Now the notifications have feedtragon/superfeedr/feed/ as an endpoint, they are reaching the sinatra app. But they are still 404ing:

@40000000555e2b74397b8da4 198.58.99.82, 198.58.99.82 - - [21/May/2015:21:00:58 +0200] "POST /feedtragon/superfeedr/feed/232 HTTP/1.1" 404 18 0.0017

It is as if superfeedr.on_notification do |feed_id, body, url, request| would not work, either listening at the wrong place, or not at all.

That might be more a general sinatra/rack thing and might be related to my server setup, sorry if that's the case.

PS: I also tried to set Rack::Superfeedr.base_path in Sinatras configure block (which I'd like to avoid, because the url-helper does not work there), that did not help.

@julien51
Copy link
Member

Onli, let me check this and get back to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants