04-09-2020 05:52 AM
Can anyone tell me what this is? Blocked By X-Frame Options ...
I had a watcher on an item so I went into the listing to revise it and change the selling price when I seen it. I've never seen it before... I've had no to very few sales lately so just wondering.
Blocked By X-Frame Options
04-09-2020 07:25 AM - edited 04-09-2020 07:28 AM
Do you have an add-on for translation capability? If so, that may be your problem. Many of the add-ons allow 'execute remote code' capability, which isn't allowed by some browsers.
04-09-2020 07:42 AM
04-09-2020 12:55 PM
It's just more eBay funky code - in this case the frame tag HTML for dividing various bits of a page into sections with their own attributes. There actually isn't anything that's being added or taken away materially from the listing page, it's just bad coding. I just ignore it.
04-09-2020 05:44 PM - edited 04-09-2020 05:47 PM
I'm a seller and thank you for the just ignore reply. We pay ebay up to 12% for each sale they don't pay us a dime they should leave us alone and quit "Telling" us how to list!!!
04-10-2020 01:56 PM
Just throw the rules out the window huh?
04-10-2020 01:59 PM
Assuming this is true (which is a big assumption), thank you. This and the hacker one are the two best explanations I've heard so far.
04-10-2020 05:15 PM
The eBay iframe that is being blocked by cross-site-scripting rules carries the label "product_insights_summary_iframe". That leads me to believe that ebay uses that little window to display pricing suggestions. We all need that, right?
I don't see the problem in my Firefox browser, so the blocking may be browser specific. Could it be in only Google Chrome? The ebay site where my listing editing occurs is "bulksell.ebay.com" whereas the site where the iframe document is located is "ebay.com". Since the two domains don't match, the browser is blocking to prevent "cross-site" scripting across two different sites.
04-10-2020 08:11 PM
I see the problem in Firefox, and reading the frame code is rather interesting, and the chattiest code I've seen for a while, though granted I'm as rusty as an old hinge.
04-15-2020 08:53 AM
04-15-2020 02:12 PM
04-15-2020 04:55 PM
have the same issue on multiple listing,,
you need to have the item number take a picture or copy and paste
then contact eBay customer service with that information
do not ignore this it`s not the browser or any add on
Hacking a eBay listing is a serious offense plus you do not want your information
out in the open,,,
this is what Customer Service told me what to do
when I got eBay on line I did not have the listing number so I refresh the page to get the number
for some reason when I got back on the revise page the(Blocked by X-Frame-Options)
had gone away and eBay could not see it,,
I will get all my info next time I call eBay so they could see that message
will come back with some result to keep you and every one else informed
thanks
eBay Member that care
be safe out there
04-18-2020 06:30 AM
I have the "Blocked by X-Frame-Options" message in all of my listings. I view my listings and revise them in Firefox. Somehow I think eBay is screwing us over. Some how. Some way.
04-18-2020 10:22 AM
Google says Firefox 75 is the latest version, which was released on April 7, 2020.
I have an older version and don't see the warning message on the listing creation page.
The message is not an indication of hacking. It is an indication that new browser rules are in place and are affecting the display of frame content. It appears that the frame content that is being blocked likely consists of pricing recommendations, which most sellers ignore anyway. However, to get to the bottom of this, we need to know if everyone noticing the issue is experiencing the same thing using the same browser version.
04-18-2020 10:46 AM
@estore2 wrote:I have the "Blocked by X-Frame-Options" message in all of my listings. I view my listings and revise them in Firefox. Somehow I think eBay is screwing us over. Some how. Some way.
No, no one is screwing us over and there are no hackers - it's purely a content and conventions issue as @shipscript says. As a matter of fact, the odd message did pop up after my recent Firefox update.