Remote widget 403 error page

Thanks. Here is the link to the actual page the remote widget is calling in.

http://www.jackpotpost.com/linked_ads...

The table is set at 100% and the widget is set for 400 by 400 so I figured it would be the size I set for the widget. Also I dropped in the code for dynamic sizing to see if that was the issue and that didn't work either.

The URL for the widget is

http://www.widgetbox.com/widget/jpfea...

Yup, looks like your PHP page is puking on the query string:

http://www.jackpotpost.com/linked_ads...

You'll need to make your page handle the query string properly.

Two things, first, what query string and second I have another remote widget that is have almost the same problem.

http://www.widgetbox.com/widget/postt...

When we iframe in your page, we have to pass it a ton of information (all config params, size, etc.) in case you need to use that. The link I posted above has an example query string that we pass along to any URL we iframe in.

Your other widget has exactly the same problem. It's failing to handle the query string.

Okay,

Here are all the parameters that I could find from the link you sent me...

widget.appId=

widget.regId=

widget.friendlyId=

widget.token=

widget.id=

widget.location=

widget.timestamp=

widget.provServiceLevel=

widget.instServiceLevel=

widget.width=

widget.height=

widget.wrapper=

widget.adPlacement=

Everything has a value except widget.adPlacement

but my question is, what do I need to do to act on any of this?

Nothing, other than your page needs to not freak out if it gets these parameters as well as any others. Whoever did your PHP should be able to handle this no problem.

It looks like the value of widget.location is what you're having trouble with. just make it handle potential values more gracefully.

It is the slashes in the url for the location that is crashing the page. Can you point me in the right direction on what I need to do about that ?

Hi Robin,

Sorry, but PHP isn't really my expertise. :(

Well for the next people that ask:

AllowEncodedSlashes On

working on how to implement this on my server

I have tech support at my hosting company looking into this, but it seems a poor way to have the remote widgets work as Apache is set by default with AllowEncodedSlashes set to Off. Why do you pass the url of the widget where it is referenced on Widgetbox to the page that is being called in?

The url for the widget is set by the widget creator, so this would be information they could hard code into the page if needed. Since by default this won't work on Apache servers, it seems pointless to send this data. I am of course working around your configuration, but did want to point out that those who would need to use the widget url would know what it is because they created it.

The user does not create this value, nor do they have access to tamper with it. This configuration is what has worked for developers (Apache and otherwise) for some years now.

You are wrong about the user creating this value. Not only does the user create this but they can change it as well. I just did.

the widget URL that is passed to the page is the URL set by the creator when they make the widget. In this case

http%3A%2F%2Fwww.widgetbox.com%2Fwidget%2Fjpfeatured

Here is what it looks like before you set it:

Jackpot Post Linked Ads

http://www.widgetbox.com/widget/{url not set}

so again, there is no reason to post that information, as the creator would know that information and could hard code the info if needed.

and I can't be the only person that has run into this. Most people probably do what I did to begin with and move on figuring that it just doesn't work...