Community

Iframe doesn't work in second domain in Firefox

NodeBB Development
  • B

    I have two domains, one the forum works in any browser, The second domain doesn't work in Firefox.
    I'm using iframe to display the forum.
    First method http://forum.imjetset.com/

    <?php
function url_origin( $s, $use_forwarded_host = false )
{
    $ssl      = ( ! empty( $s['HTTPS'] ) && $s['HTTPS'] == 'on' );
    $sp       = strtolower( $s['SERVER_PROTOCOL'] );
    $protocol = substr( $sp, 0, strpos( $sp, '/' ) ) . ( ( $ssl ) ? 's' : '' );
    $port     = $s['SERVER_PORT'];
    $port     = ( ( ! $ssl && $port=='80' ) || ( $ssl && $port=='443' ) ) ? '' : ':'.$port;
    $host     = ( $use_forwarded_host && isset( $s['HTTP_X_FORWARDED_HOST'] ) ) ? $s['HTTP_X_FORWARDED_HOST'] : ( isset( $s['HTTP_HOST'] ) ? $s['HTTP_HOST'] : null );
    $host     = isset( $host ) ? $host : $s['SERVER_NAME'] . $port;
    return $protocol . '://' . $host;
}

function full_url( $s, $use_forwarded_host = false )
{
    return url_origin( $s, $use_forwarded_host ) . $s['REQUEST_URI'];
}

$absolute_url = full_url( $_SERVER );
$url = str_replace("forum.imjetset.com", "forum.superaffiliatesystem.com", $absolute_url);
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
    <head>
        <title>Jetset Forum | Affiliate Marketing Forum</title>
        <meta http-equiv="X-Frame-Options" content="allow">
        <style type="text/css">
            body, html
            {
                margin: 0; padding: 0; height: 100%; overflow: hidden;
            }

            #content
            {
                position:absolute; left: 0; right: 0; bottom: 0; top: 0px; 
            }
        </style>
    </head>
    <body>
        <div id="content">
            <iframe width="100%" height="100%" frameborder="0" src="<?php echo $url; ?>" />
            <div id="result"></div>
        </div>
    </body>
</html>

    Second method http://forum.imjetset.com/index1.php

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
    <head>
        <title>Jetset Forum | Affiliate Marketing Forum</title>
        <meta http-equiv="X-Frame-Options" content="allow">
        <style type="text/css">
            body, html
            {
                margin: 0; padding: 0; height: 100%; overflow: hidden;
            }

            #content
            {
                position:absolute; left: 0; right: 0; bottom: 0; top: 0px; 
            }
        </style>
    </head>
    <body>
        <div id="content">
            <iframe width="100%" height="100%" frameborder="0" src="http://forum.superaffiliatesystem.com" />
            <div id="result"></div>
        </div>
    </body>
</html>

    Third method - http://forum.imjetset.com/index2.php

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
    <head>
        <title>Jetset Forum | Affiliate Marketing Forum</title>
        <meta http-equiv="X-Frame-Options" content="allow">
        <style type="text/css">
            body, html
            {
                margin: 0; padding: 0; height: 100%; overflow: hidden;
            }

            #content
            {
                position:absolute; left: 0; right: 0; bottom: 0; top: 0px; 
            }
        </style>
    </head>
    <body>
        <div id="content">
            <iframe width="100%" height="100%" frameborder="0" src="http://52.41.178.169" />
            <div id="result"></div>
        </div>
    </body>
</html>

    Neither method works, does anyone have any idea how I could do to fix this? Google Chrome works correctly

    PitaJP 1 Reply
    0
  • PitaJP

    @Braulio-Cesar-Holtz-Ribeiro you need to set the HTTP header for frame options on the site that is displayed inside the iframe.

    NodeBB actually has a setting for this in the ACP. You should be able to find it by searching "frame"

    0

Suggested Topics

  • Casey Chen LaiC

    I'd like to translate NodeBB into Cantonese, but how?

    NodeBB Development
    0 Votes
    6 Posts
    366 Views
    julianJ

    @Casey-Chen-Lai You'll want to translate to zh-TW, which is our traditional chinese variant.

    Don't ask me why it's TW and not HK.

    zh-TW is available for translation in Transifex, let me know if you run into additional issues 🙂

  • epidemiya30E

    What is for ''/compose" route?

    Solved NodeBB Development
    0 Votes
    3 Posts
    1383 Views
    epidemiya30E

    Understood. Thank you for response 🙂

  • A

    Don't get new topic POST request by Chrome.

    NodeBB Development
    0 Votes
    5 Posts
    2318 Views
    A

    1、Can I get data format？
    2、websocket use port 80？
    3、Can I write a test example to send topic by websocket ?

  • M

    NodeBB's Usage of Realtime Communication

    NodeBB Development
    1 Votes
    1 Posts
    1044 Views
    M

    Something that interested me when I first started hacking on NodeBB was how the platform uses realtime communication through socket.io (and websockets). This interest stems from work I did whilst working as a realtime engineer at Pusher several years ago. One of my research projects whilst there was to look into how websockets get used in production, and other use cases for websockets besides the standard "subscribe to a channel and receive events".

    In 2011, I gave a talk at Keeping It Realtime conference in portland about some of my findings, you can watch it here: http://2011.krtconf.com/videos/micheil_smith (long hair and all) or check out the slides here: https://speakerdeck.com/miksago/krtconf-websockets-sub-protocols

    How NodeBB currently seems to use realtime communication:

    RPC: Request data from the server, get a response back, present that data to the user (or send data to a server like you would POST to a HTTP server) Channels: Used for user to user chat messages Events: Used for online/offline states of users.

    I may have missed something here, so, let me know if I have.

    Most of the websocket usage appears to be in RPC style messages: Get this piece of data do something with it. At present, all realtime communication for NodeBB is built on top of Socket.io, which uses a protocol more tailored for event type packets, rather than for RPC style packets. For this, something like JSON RPC may be more appropriate.

    Refactoring this deep internal of NodeBB would make the platform more resource efficient on the wire, and also allow for better logging and handling of data. You'd know exactly what has failed on the client-side or server-side and be able to give an appropriate response. In the code, refactoring this level of things would make the code far cleaner, and give option to provide all HTTP Verbs over WebSocket or vica-verse (meaning if you wanted to, you could make 90% of NodeBB standard HTTP. You'd end up with an "api" module internally that is everything that can be exposed, which simple returns back standard javascript objects.

    For user-to-user chat messaging you could still multiplex that onto the same actual websocket / socket.io connection (although it's arguable if this is actually beneficial).

    Why do any of this writing or work? Interest more than anything else, but it may make the code to NodeBB cleaner, and improve maintainability.

  • psychobunnyP

    NodeBB's Next Theme

    Moved NodeBB Development
    2 Votes
    33 Posts
    22949 Views
    HolyPhoenixH

    Will there be a new theme for version .5?

    Just curious (from an excitement for the next version standpoint). The current themes are already leaps and bounds better than other forum scripts.

Copyright © 2023 NodeBB | Contributors